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

Posted to dev@phoenix.apache.org by "Ankit Singhal (JIRA)" <ji...@apache.org> on 2016/12/08 07:01:58 UTC

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

Ankit Singhal created PHOENIX-3525:
--------------------------------------

             Summary: 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.3.4#6332)