[
https://issues.apache.org/jira/browse/PHOENIX-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095335#comment-16095335
]
James Taylor commented on PHOENIX-3525:
---------------------------------------
bq. It the batchTime is HConstants.LATEST_TIMESTAMP then I am using the
timestamp returned by updateIndexState call.
If HConstants.LATEST_TIMESTAMP is returned, use the timestamp returned by
updateIndexState. Otherwise, use the min of the timestamp returned by the
updateIndexState call and the timestamp returned by getTimestampForBatch. The
timestamp returned by getTimestampForBatch is simply the last min timestamp
value plus the configurable period of time (which might be beyond what it needs
to be).
> 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
> Attachments: PHOENIX-3525_wip.patch
>
>
> From [[email protected]] 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)
