[
https://issues.apache.org/jira/browse/PHOENIX-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16875625#comment-16875625
]
Hudson commented on PHOENIX-5373:
---------------------------------
FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-1.4 #202 (See
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.4/202/])
PHOENIX-5373 GlobalIndexChecker should treat the rows created by the (kadir:
rev 789930617cdfe3f435b3331817cc4996d27a9368)
* (edit)
phoenix-core/src/it/java/org/apache/phoenix/end2end/IndexExtendedIT.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/index/GlobalIndexChecker.java
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/IndexToolIT.java
* (edit)
phoenix-core/src/it/java/org/apache/phoenix/end2end/CsvBulkLoadToolIT.java
* (edit)
phoenix-core/src/it/java/org/apache/phoenix/end2end/RegexBulkLoadToolIT.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java
* (edit) phoenix-core/src/it/java/org/apache/phoenix/util/IndexScrutinyIT.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/query/QueryServicesOptions.java
> GlobalIndexChecker should treat the rows created by the previous design as
> unverified
> --------------------------------------------------------------------------------------
>
> Key: PHOENIX-5373
> URL: https://issues.apache.org/jira/browse/PHOENIX-5373
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0, 4.14.2
> Reporter: Kadir OZDEMIR
> Assignee: Kadir OZDEMIR
> Priority: Major
> Fix For: 4.15.0, 5.1.0
>
> Attachments: PHOENIX-5373.4.x-HBase-1.4.001.patch,
> PHOENIX-5373.4.x-HBase-1.4.002.patch, PHOENIX-5373.master.001.patch,
> PHOENIX-5373.master.002.patch
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> For the ease of transition from the old global secondary index design to the
> new one (without having read performance impact), GlobalIndexChecker treats
> existing index rows (i.e., the rows created by the previous design) as
> verified. We have discovered that this would lead to keeping stale index rows
> around forever and including them in the result of queries. A stale index row
> is a row for which we do not have the corresponding data table row. The
> reason that we do not have the data table row is either the row is deleted
> (but not the corresponding index row(s)), or the data table and index rows
> are written with different timestamps. The assumption was that such rows
> would be fixed by index rebuild. Unfortunately, without dropping or
> truncating index tables, these stale rows may not be fixed by index rebuild.
> Thus, GlobalIndexChecker should treat the rows created by the previous design
> as unverified.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
