[jira] [Updated] (PHOENIX-6001) Incremental rebuild/verification can result in missing rows and false positives

["Abhishek Singh Chouhan (Jira)" <ji...@apache.org>]

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

Abhishek Singh Chouhan updated PHOENIX-6001:
--------------------------------------------
    Attachment: PHOENIX-6001-4.x.patch

> Incremental rebuild/verification can result in missing rows and false positives 
> --------------------------------------------------------------------------------
>
>                 Key: PHOENIX-6001
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6001
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.16.0
>            Reporter: Abhishek Singh Chouhan
>            Assignee: Abhishek Singh Chouhan
>            Priority: Critical
>             Fix For: 5.1.0, 4.16.0
>
>         Attachments: PHOENIX-6001-4.x.patch
>
>
> In case of incremental rebuild/verify we prepare a skip scan using page size constraints first and then use it for rebuild, however when using this skip scan we constraint the number of indexmutations we're going to build/verify also on the page size. In the case where we have multiple index mutations for single dataTableRow, we can return back to the client without scanning all the rows of the skip scan filter, when the client does next, we resume incorrectly from the row after the last of the previous skip scan when infact we hadn't exhausted it fully.   



--
This message was sent by Atlassian Jira
(v8.3.4#803005)