[CARBONDATA-3911]Fix NullPointerException in case of multiple updates and clean files #3843
Conversation
|
Build Success with Spark 2.3.4, Please check CI http://121.244.95.60:12545/job/ApacheCarbonPRBuilder2.3/3390/ |
|
Build Success with Spark 2.4.5, Please check CI http://121.244.95.60:12545/job/ApacheCarbon_PR_Builder_2.4.5/1649/ |
akashrn5
changed the title
akashrn5
force-pushed
the
update_clean_files
branch
from
2740e6a
to
41eee88
Compare
|
Build Success with Spark 2.3.4, Please check CI http://121.244.95.60:12545/job/ApacheCarbonPRBuilder2.3/3412/ |
|
Build Success with Spark 2.4.5, Please check CI http://121.244.95.60:12545/job/ApacheCarbon_PR_Builder_2.4.5/1670/ |
|
retest this please |
|
Build Failed with Spark 2.3.4, Please check CI http://121.244.95.60:12545/job/ApacheCarbonPRBuilder2.3/3462/ |
|
Build Success with Spark 2.4.5, Please check CI http://121.244.95.60:12545/job/ApacheCarbon_PR_Builder_2.4.5/1720/ |
|
retest this please |
|
Build Success with Spark 2.3.4, Please check CI http://121.244.95.60:12545/job/ApacheCarbonPRBuilder2.3/3466/ |
|
Build Success with Spark 2.4.5, Please check CI http://121.244.95.60:12545/job/ApacheCarbon_PR_Builder_2.4.5/1724/ |
|
LGTM |
Why is this PR needed?
when multiple load and multiple updates are performed, the segment files will be created for each update, when clean files performed, if two segments are there, first segment will clean other segments's segment file also which leads to nullpointer.
What changes were proposed in this PR?
Once all the segments stale segment files are collected, then delete the stale files at once.
Does this PR introduce any user interface change?
Is any new testcase added?