tree 1f6d38229358e013a8fd2053978e420803607db8
parent 070d7e70fa8aa88815825bbbccb4ba86eedc5d4a
author ajantha-bhat <ajanthabhat@gmail.com> 1581736362 +0530
committer Jacky Li <jacky.likun@qq.com> 1582644433 +0800

[CARBONDATA-3637] Use optimized insert flow for MV and insert stage command

Why is this PR needed?
MV and insert stage can use the new optimized insert into flow.

Also In the new insert into flow, found one issue with the partition column. Fixed it.

If the catalog table schema is already rearranged, don't rearrange again.
Timestamp converter was not handled for 0 value. Need to set it to Null when it is 0.
While deriving the index for the convert to 3 step for new insert flow, order was based on internal partition order, instead of internal order.

What changes were proposed in this PR?

changed MV and insert stage command to use optimized insert flow.

After this changes,
b. CarbonInsertIntoCommand -- insert DML, CTAS DML, MV, insert stage command.
c. CarbonInsertIntoWithDf -- old flow which supports bad record handling with converter step method that process update, compaction, df writer, alter table scenarios [some problem in rearranging now]

Does this PR introduce any user interface change?
No

Is any new testcase added?
No

This closes #3615