[
https://issues.apache.org/jira/browse/PHOENIX-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16111757#comment-16111757
]
Vincent Poon commented on PHOENIX-4057:
---------------------------------------
[~jamestaylor] I guess this would also mean we can't run a scrutiny as of an
older timestamp? As that would essentially be a point-in-time query comparison
of data vs index table, and there could potentially be data table writes
without corresponding index updates with this change?
> Do not issue index updates for out of order mutation during index maintenance
> ------------------------------------------------------------------------------
>
> Key: PHOENIX-4057
> URL: https://issues.apache.org/jira/browse/PHOENIX-4057
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: James Taylor
> Fix For: 4.12.0, 4.11.1
>
> Attachments: PHOENIX-4057_v1.patch, PHOENIX-4057_wip1.patch
>
>
> Index maintenance is not correct when rows arrive out of order (see
> PHOENIX-4052). In particular, out of order deletes end up with a spurious Put
> in the index. Rather than corrupt the secondary index, we can instead just
> ignore out-of-order mutations. The only downside is that point-in-time
> queries against an index will not work correctly.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
