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

Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2017/09/20 16:37:00 UTC

[jira] [Updated] (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:all-tabpanel ]

James Taylor updated PHOENIX-4220:
----------------------------------
    Attachment: PHOENIX-4220.patch

Please review, [~samarthjain]. I have a test with my fix for PHOENIX-4215 and  PHOENIX-4178 that I'll cleanup and submit today too, but I wanted to peel off just this fix as it's an important one for SFDC. FYI, [~vincentpoon].

> 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)