[ https://issues.apache.org/jira/browse/PHOENIX-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Taylor updated PHOENIX-3525: ---------------------------------- Labels: secondary_index (was: ) > 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 > Assignee: James Taylor > Labels: secondary_index > Fix For: 4.12.0, 4.11.1 > > Attachments: PHOENIX-3525_v1.patch, PHOENIX-3525_wip.patch, > PHOENIX-3525_wip2.patch > > > From [~chrajeshbab...@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)