phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4220) Upper bound not being used in partial index rebuilder
Date Thu, 21 Sep 2017 18:13:00 GMT

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

Hudson commented on PHOENIX-4220:
---------------------------------

FAILURE: Integrated in Jenkins build Phoenix-master #1806 (See [https://builds.apache.org/job/Phoenix-master/1806/])
PHOENIX-4220 Upper bound not being used in partial index rebuilder (jtaylor: rev 3ed60237e9685a6cab8a4bf9b8f71ba015fb710c)
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/index/PartialIndexRebuilderIT.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/coprocessor/MetaDataRegionObserver.java


> 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, PHOENIX-4220_v2.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)

Mime
View raw message