You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "rajeshbabu (JIRA)" <ji...@apache.org> on 2014/10/27 19:02:34 UTC

[jira] [Updated] (PHOENIX-1170) Change status of local index during splitting to prevent usage when slower than query through data table

     [ https://issues.apache.org/jira/browse/PHOENIX-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

rajeshbabu updated PHOENIX-1170:
--------------------------------
    Attachment: PHOENIX-1170.patch

> 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
>         Attachments: PHOENIX-1170.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)