Due to jira connection problems (and losing them twice), sending them by mail.
You can copy in the jira when it is stable:
Looks good - some minor comments.
1. Negative: exit at first error, so have a separate file for each case.
2. Positive: Output not deterministic
Add describe also.
CTAS_COLLST_COEXISTENCE("Create table as select command cannot specify the list of columns for the target table."),
CTLT_COLLST_COEXISTENCE("Create table like command cannot specify the list of columns for the target table."),
Why not ? If it is not supported currently, but you want to add it in a follow-up, can you file a jira for that ?
This affects the ReplicationHook which is used for logging statements.
For CTAS, the output should be the final table which is created - currently, it is the directory – needs
to be investigated
4370 if ( ! oneLoadFile )
4371 // should not have more than one files to load
4372 throw new SemanticException(ErrorMsg.CTAS_MULTI_LOADFILE.getMsg());
The above error is not really a exception - it can be a assert
Currently, for non CTAS create tables, root tasks are created by analyzeCreateTable, whereas for CTAS,
it is created later on – can you file a new jira for this cleanup.