phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-4057) Do not issue index updates for out of order mutation
Date Tue, 01 Aug 2017 23:44:00 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

James Taylor updated PHOENIX-4057:
----------------------------------
    Attachment: PHOENIX-4057_v1.patch

Patch that prevents index updates for out-of-order rows (since the index was already done
for the newer rows). Attempts to make minimal changes to Indexer code since it would be nice
to get it working correctly so that point in time queries will work. If we give up on that,
we can simplify the indexing code substantially.

Please review, [~vincentpoon] and/or [~samarthjain].

[~mujtabachohan] - would you mind giving this patch a try?

> Do not issue index updates for out of order mutation
> ----------------------------------------------------
>
>                 Key: PHOENIX-4057
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4057
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>         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)

Mime
View raw message