[
https://issues.apache.org/jira/browse/CARBONDATA-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17268547#comment-17268547 ]
Ajantha Bhat commented on CARBONDATA-4105:
------------------------------------------
Here in a spark cluster JVM itself you are running SDK read and write. Hence this problem.
Ideally, when you run SDK in the cluster it will span up its own JVM. so spark cluster will not be affected.
I don't think this issue has to be fixed as it is not a user scenario.
> Select * query fails after a SDK written segment is added by alter table add segment query.
> -------------------------------------------------------------------------------------------
>
> Key: CARBONDATA-4105
> URL:
https://issues.apache.org/jira/browse/CARBONDATA-4105> Project: CarbonData
> Issue Type: Bug
> Components: core
> Reporter: Karan
> Priority: Major
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> When a SDK written segment on which read is already performed once, is added through alter table add segment query to a carbon table, then select * query fails after adding it.
> In SDK segments the segmentId is the timestamp of the segment. When the SDK segment is read before adding, its indexes are stored in cache. Cache is a map of indexFilePath to Indexes. Now when the same segment is added to carbon table its segment ID is no longer the timestamp but the indexFilePath remains same as it is added externally. Now when we run select * query we get the indexes from the cache, but it is unable to map it to segment, because segment id changes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Locked
