[
https://issues.apache.org/jira/browse/PHOENIX-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14186002#comment-14186002
]
Hudson commented on PHOENIX-1170:
---------------------------------
SUCCESS: Integrated in Phoenix | Master #463 (See
[https://builds.apache.org/job/Phoenix-master/463/])
PHOENIX-1170 Change status of local index during splitting to prevent usage
when slower than query through data table (Rajeshbabu) (jtaylor: rev
a1685c4f5413d38a81da08945b736d554efb8ab8)
*
phoenix-core/src/main/java/org/apache/hadoop/hbase/regionserver/LocalIndexSplitter.java
* phoenix-core/src/it/java/org/apache/phoenix/end2end/index/LocalIndexIT.java
* phoenix-core/src/test/java/org/apache/phoenix/query/BaseTest.java
* phoenix-core/src/it/java/org/apache/phoenix/end2end/QueryIT.java
*
phoenix-core/src/main/java/org/apache/hadoop/hbase/regionserver/IndexHalfStoreFileReaderGenerator.java
> Change status of local index during splitting to prevent usage when slower
> than query through data table
> --------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-1170
> URL: https://issues.apache.org/jira/browse/PHOENIX-1170
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Assignee: rajeshbabu
> Fix For: 5.0.0, 4.2
>
> Attachments: PHOENIX-1170.patch, PHOENIX-1170_v2.patch
>
>
> Without pre-split, queries to the table take 9x more time (i.e. 1 sec versus
> 9sec) for a count(*). If we can't bring the time down to be less than a full
> scan over the data table, we should update the local index status as INACTIVE
> while it's splitting, then it wouldn't be used for queries, but it would
> continue to be maintained. Then when the split is done, we could move it back
> to ACTIVE. Alternatively, we could invent a new status, like SPLITTING, and
> only use the local index for point lookups until the status is back to ACTIVE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
