phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kadir OZDEMIR (Jira)" <j...@apache.org>
Subject [jira] [Assigned] (PHOENIX-5505) Index read repair does not repair unverified rows with higher timestamp
Date Tue, 01 Oct 2019 20:49:00 GMT

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

Kadir OZDEMIR reassigned PHOENIX-5505:
--------------------------------------

    Assignee: Kadir OZDEMIR

> Index read repair does not repair unverified rows with higher timestamp 
> ------------------------------------------------------------------------
>
>                 Key: PHOENIX-5505
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5505
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 5.0.0, 4.15.0, 4.14.3
>            Reporter: Kadir Ozdemir
>            Assignee: Kadir OZDEMIR
>            Priority: Major
>
> Read repair (GlobalIndexChecker) sets the time range for the scan on the data table for
using the timestamp of the index table row to be repaired. The start time for the scan is
the timestamp of the index row in the current implementation. However, if the index row timestamp
is higher than the data table row timestamp, then the data table row will not be visible to
the scan. The index row timestamp can be higher when the index row is overwritten with the
unverified row status (in the first write phase) but the data table row is not overwritten
(in the second write phase) due to a failure. In this case, the unverified index row will
not be rebuilt and will be deleted eventually.



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

Mime
View raw message