[
https://issues.apache.org/jira/browse/PHOENIX-5736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039531#comment-17039531
]
Kadir OZDEMIR commented on PHOENIX-5736:
----------------------------------------
[~comnetwork], please check the attached test code. [~gjacoby] is looking into
the skip scan issue to find out if it is a Phoenix or an HBase issue and if it
can be fixed quickly. I think this is an HBase issue as I have experienced that
any filter on a raw scan is not reliable. I think we should revert PHOENIX-5494
meanwhile. Please let me know if you have any input on this. [~larsh], FYI ...
> Mutable global index rebuilds are incorrect after PHOENIX-5494
> --------------------------------------------------------------
>
> Key: PHOENIX-5736
> URL: https://issues.apache.org/jira/browse/PHOENIX-5736
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0, 4.15.0, 4.14.3
> Reporter: Kadir OZDEMIR
> Priority: Critical
> Attachments: skipScanTest.txt
>
>
> PHOENIX-5494 uses skip scans to improve write performance for tables with
> indexes. Before this jira, a separate scanner was opened for each data table
> mutation to read all versions and delete markers of for the row to be
> mutated. With this jira, a single scanner is opened using a raw scan with a
> skip scan filter to read all versions and delete markers of the all rows in a
> batch. Reading existing data table rows is required to generate index updates.
> However, I have discovered that a raw scan with a skip scan filter does not
> return all raw versions. This means that after PHOENIX-5494 index rebuilds
> for global indexes will not be correct.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
