[
https://issues.apache.org/jira/browse/PHOENIX-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16111984#comment-16111984
]
Hudson commented on PHOENIX-4057:
---------------------------------
FAILURE: Integrated in Jenkins build Phoenix-master #1726 (See
[https://builds.apache.org/job/Phoenix-master/1726/])
PHOENIX-4057 Do not issue index updates for out of order mutation (jamestaylor:
rev e494fe9fa744ec2948cf75b007e92fef0b1ba829)
* (edit)
phoenix-core/src/it/java/org/apache/phoenix/hbase/index/covered/example/EndToEndCoveredIndexingIT.java
* (edit)
phoenix-core/src/it/java/org/apache/phoenix/end2end/ConcurrentMutationsIT.java
* (add)
phoenix-core/src/it/java/org/apache/phoenix/end2end/OutOfOrderMutationsIT.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/hbase/index/covered/NonTxIndexBuilder.java
> 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)
