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

Posted to dev@phoenix.apache.org by "Vincent Poon (JIRA)" <ji...@apache.org> on 2017/09/20 17:28:00 UTC

[jira] [Commented] (PHOENIX-4220) Upper bound not being used in partial index rebuilder

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

Vincent Poon commented on PHOENIX-4220:
---------------------------------------

Is there a test we can write for this? We didn't have one on PHOENIX-3525 , so didn't catch this.
But +1 to the patch!

> Upper bound not being used in partial index rebuilder
> -----------------------------------------------------
>
>                 Key: PHOENIX-4220
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4220
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>             Fix For: 4.12.0
>
>         Attachments: PHOENIX-4220.patch
>
>
> Though we're setting the scan upper and lower bound, it's not taking effect in the index rebuilder. Thus, we're rebuilding from the lower bound to the latest timestamp which is bad if the table is taking a lot of writes.



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