tree 6fffff871e4ccbab5a7f708627e74102a05cc1d7
parent 2bfbc01ce8251ba498611ce39fcd0ef8df69b311
author Mahesh Raju Somalaraju <mahesh.somalaraju@huawei.com> 1593188270 +0530
committer akashrn5 <akashnilugal@gmail.com> 1594120858 +0530

[CARBONDATA-3874] segment mismatch between maintable and SI table when load with concurrency

Why is this PR needed?
1. segment mismatch between main table and SI table with concurrency loads
2. In concurrent loads, if one of the load failed for SI table then 'isSITableEnabled' will be
disabled(isSITableEnabled = false). So in failed SI event listener case we are just checking SI
enabled is true(isSITableEnabled == true) then we are not loading current load to SI table. In
concurrent scenarios, this might be happening as SI enabled state is true but segment difference may exist.

What changes were proposed in this PR?
So instead of checking just SI enabled is true(isSITableEnabled == true) we should also check if any
segment difference between main table and SI table. The final output flag checking will be as follows.
if ( isSITableEnabled == true || mainTblAndSidiff == true ) { --- }

This closes #3811