Internal error when load command is used on non-default schema

Bug #1439779 reported by Suresh Subbiah on 2015-04-02
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Trafodion
New
Medium
Suresh Subbiah

Bug Description

set schema sch ;

>>load into G_TPCH2X.customer1 select * from hive.hive.customer ;
..
Task: LOAD Status: Started Object: TRAFODION.G_TPCH2X.CUSTOMER1
Task: CLEANUP Status: Started Object: TRAFODION.G_TPCH2X.CUSTOMER1
Task: CLEANUP Status: Ended Object: TRAFODION.G_TPCH2X.CUSTOMER1
Task: DISABLE INDEXE Status: Started Object: TRAFODION.G_TPCH2X.CUSTOMER1

*** ERROR[2006] Internal error: assertion failure (schemaNamePart == currSchName) in file at line -99999.

Problem is easy to reproduce and should happen with any table. If the source table is on a schema that is different from the current default schema then this error is seen.

It is interesting to note that the following statement does NOT raise this error
 >>load with no populate indexes into G_TPCH2X.customer1 select * from hive.hive.customer ;
Task: LOAD Status: Started Object: TRAFODION.G_TPCH2X.CUSTOMER1
Task: CLEANUP Status: Started Object: TRAFODION.G_TPCH2X.CUSTOMER1
Task: CLEANUP Status: Ended Object: TRAFODION.G_TPCH2X.CUSTOMER1
Task: PREPARATION Status: Started Object: TRAFODION.G_TPCH2X.CUSTOMER1
....

Changed in trafodion:
assignee: khaled Bouaziz (khaled-bouaziz) → Suresh Subbiah (suresh-subbiah)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers