[jira] [Commented] (PHOENIX-3525) Cap automatic index rebuilding to inactive timestamp.

["James Taylor (JIRA)" <ji...@apache.org>]

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

James Taylor commented on PHOENIX-3525:
---------------------------------------

[~samarthjain] - this is the JIRA we were discussing. Rather than using the timestamp at which the index was marked active, I'd lean toward adding a new INDEX_ENABLED_TIMESTAMP instead so that we can handle the case of keeping the index active.

> Cap automatic index rebuilding to inactive timestamp.
> -----------------------------------------------------
>
>                 Key: PHOENIX-3525
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3525
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Ankit Singhal
>
> From [~chrajeshbabu32@gmail.com] review comment on 
> https://github.com/apache/phoenix/pull/210
> For automatic rebuilding ,DISABLED_TIMESTAMP is lower bound but there is no upper bound so we are going rebuild all the new writes written after DISABLED_TIMESTAMP even though indexes updated properly. So we can introduce an upper bound of time where we are going to start a rebuild thread so we can limit the data to rebuild. In case If there are frequent writes then we can increment the rebuild period exponentially



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)