You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/05/11 14:45:13 UTC

[jira] [Commented] (PHOENIX-2890) Extend IndexTool to allow incremental index rebuilds

    [ https://issues.apache.org/jira/browse/PHOENIX-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15280249#comment-15280249 ] 

James Taylor commented on PHOENIX-2890:
---------------------------------------

Partial index rebuild is different because it needs to "replay" all data table mutations by doing a raw scan (see the code comments). This is necessary because the incrememtal index maintanence failed. The IndexTool only needs to generate the index rows for existing data rows as incrememtal index maintenance is being done on new data coming in.

> Extend IndexTool to allow incremental index rebuilds
> ----------------------------------------------------
>
>                 Key: PHOENIX-2890
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2890
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Ankit Singhal
>            Priority: Minor
>
> Currently , IndexTool is used for initial index rebuild but I think we should extend it to be used for recovering index from last disabled timestamp too. 
> In general terms if we run IndexTool on already existing/new index, then it should follow the same semantics as followed by background Index rebuilding thread.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)