[
https://issues.apache.org/jira/browse/CARBONDATA-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikram Ahuja updated CARBONDATA-4099:
-
Description:
There were 2 issues in the clean files post event listener:
# In concurrent cases, while writing entry back to the table status file,
wrong path was given, due to which table status file was not updated in the
case of SI table.
# While writing the loadmetadetails to the table status file during concurrent
scenarios, we were only writing the unwanted segments and not all the segments,
which could make segments stale in the SI table
Due to these 2 issues, when selet query is executed on SI table, the
tablestatus would have entry for a segment but it's carbondata file would be
deleted, thus throwing an IO Exception.
> Fix Concurrent issues with clean files post event listener
> --
>
> Key: CARBONDATA-4099
> URL: https://issues.apache.org/jira/browse/CARBONDATA-4099
> Project: CarbonData
> Issue Type: Bug
>Reporter: Vikram Ahuja
>Priority: Major
> Fix For: 2.2.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> There were 2 issues in the clean files post event listener:
> # In concurrent cases, while writing entry back to the table status file,
> wrong path was given, due to which table status file was not updated in the
> case of SI table.
> # While writing the loadmetadetails to the table status file during
> concurrent scenarios, we were only writing the unwanted segments and not all
> the segments, which could make segments stale in the SI table
> Due to these 2 issues, when selet query is executed on SI table, the
> tablestatus would have entry for a segment but it's carbondata file would be
> deleted, thus throwing an IO Exception.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
