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

James Taylor edited comment on PHOENIX-4144 at 8/30/17 7:24 PM:
----------------------------------------------------------------

Attach WIP patch with test that repros this potential issue. Will work on fix 
soon. FYI, [~vincentpoon].


was (Author: jamestaylor):
Attach WIP patch with test that repros this potential issue. Will work on fix 
soon.

> Query for latest version during index rebuilding
> ------------------------------------------------
>
>                 Key: PHOENIX-4144
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4144
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>         Attachments: PHOENIX-4144_wip.patch
>
>
> We're currently setting an upper bound of the scan to find the previous data 
> table row when rebuilding the index. We need to remove this upper bound, 
> though, so that we know if there are more recent versions of a data table row 
> so that we delete the row we've added. We can then process one row past our 
> current timestamp so we don't miss any deletes.



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

Reply via email to