You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@carbondata.apache.org by "Akash R Nilugal (JIRA)" <ji...@apache.org> on 2018/04/13 11:16:00 UTC
[jira] [Updated] (CARBONDATA-2347) Fix Functional issues in
LuceneDatamap in load and query and make stable
[ https://issues.apache.org/jira/browse/CARBONDATA-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Akash R Nilugal updated CARBONDATA-2347:
----------------------------------------
Description:
1) The index write location for the lucene is same, and to IndexWriter will take a lock file called write.lock in write location while writing the index files. In carbon loading the writer tasks are launched parallel and those many writers are opened,Since the write.lock file is acquired by one writer, all other tasks will fail and dataloading will fail.
2)in query side, read index path for lucene was in single path, but after load fix, there will be multiple index directories after load
functional issues in drop table, drop datamap, show datamap
> Fix Functional issues in LuceneDatamap in load and query and make stable
> ------------------------------------------------------------------------
>
> Key: CARBONDATA-2347
> URL: https://issues.apache.org/jira/browse/CARBONDATA-2347
> Project: CarbonData
> Issue Type: Bug
> Components: data-load, data-query
> Reporter: Akash R Nilugal
> Assignee: Akash R Nilugal
> Priority: Major
>
> 1) The index write location for the lucene is same, and to IndexWriter will take a lock file called write.lock in write location while writing the index files. In carbon loading the writer tasks are launched parallel and those many writers are opened,Since the write.lock file is acquired by one writer, all other tasks will fail and dataloading will fail.
> 2)in query side, read index path for lucene was in single path, but after load fix, there will be multiple index directories after load
> functional issues in drop table, drop datamap, show datamap
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)