[
https://issues.apache.org/jira/browse/PHOENIX-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997685#comment-15997685
]
Vincent Poon commented on PHOENIX-3824:
---------------------------------------
[~jamestaylor] Can you take a look at the logic in the patch? Previously, when
we ignoredNewerMutations , we set the scanner max timestamp to the first entry
in the cell list, which is the newest timestamp. But it seems for replaying of
mutations, we should be getting the oldest timestamp in the current mutation,
otherwise we'll fetch data that is in the current mutation being replayed.
> Mutable Index partial rebuild adds more than one index row for updated data
> row
> -------------------------------------------------------------------------------
>
> Key: PHOENIX-3824
> URL: https://issues.apache.org/jira/browse/PHOENIX-3824
> Project: Phoenix
> Issue Type: Bug
> Reporter: Vincent Poon
>
> If you follow this sequence:
> 1) disable index
> 2) write an updates to a data table row
> 3) trigger the BuildIndexScheduleTask partial rebuild
> then you end up with two index rows for the one data table row.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
