[
https://issues.apache.org/jira/browse/CARBONDATA-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ravindra Pesala resolved CARBONDATA-2484.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 1.4.0
> Refactor the datamap code and clear the datamap from executor on table drop
> ---------------------------------------------------------------------------
>
> Key: CARBONDATA-2484
> URL: https://issues.apache.org/jira/browse/CARBONDATA-2484
> Project: CarbonData
> Issue Type: Sub-task
> Reporter: Akash R Nilugal
> Assignee: Akash R Nilugal
> Priority: Major
> Fix For: 1.4.0
>
> Time Spent: 7h 40m
> Remaining Estimate: 0h
>
> During query, blockletDataMapFactory maintains a segmentMap which has mapping
> of
> segmentId -> list of index file, and this will be used while getting the
> extended blocklet
> by checking whether the blocklet present in the index or not.
> In case of Lucene, the datamap job will be launched and during pruning the
> segmentMap will be added
> in executor and this map will be cleared in driver when drop table is called,
> but it will not be cleared in executor.
> so when the query is fired after table or datamap is dropped, the lucene
> query fails.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
