[
https://issues.apache.org/jira/browse/PHOENIX-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-4558:
----------------------------------
Description: I believe that only global tables would have set the
INDEX_DISABLE_TIMESTAMP, thus we can add a start row of [0] and an end row of
[1] to restrict the scan to only traverse physical tables (of which there will
be few). Need to confirm that this holds true for local indexes and indexes on
views. It's not at all clear if/how partial rebuild works in these cases. See
PHOENIX-4263. (was: I believe that only global tables would have set the
INDEX_DISABLE_TIMESTAMP, thus we can add a start row of [0] and an end row of
[0][0] to restrict the scan to only traverse physical tables (of which there
will be few). Need to confirm that this holds true for local indexes and
indexes on views. It's not at all clear if/how partial rebuild works in these
cases. See PHOENIX-4263.)
> Add start/stop row for partial index rebuilder scan
> ---------------------------------------------------
>
> Key: PHOENIX-4558
> URL: https://issues.apache.org/jira/browse/PHOENIX-4558
> Project: Phoenix
> Issue Type: Improvement
> Reporter: James Taylor
> Priority: Major
>
> I believe that only global tables would have set the INDEX_DISABLE_TIMESTAMP,
> thus we can add a start row of [0] and an end row of [1] to restrict the scan
> to only traverse physical tables (of which there will be few). Need to
> confirm that this holds true for local indexes and indexes on views. It's not
> at all clear if/how partial rebuild works in these cases. See PHOENIX-4263.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
