[ 
https://issues.apache.org/jira/browse/PHOENIX-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950463#comment-16950463
 ] 

Hudson commented on PHOENIX-5515:
---------------------------------

FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #561 (See 
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.3/561/])
PHOENIX-5515 Able to write indexed value to data table without writing (kadir: 
rev 6d70c9c3d9c9014f55dea66ee7da5a92d1044b44)
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/hbase/index/IndexRegionObserver.java
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/hbase/index/write/IndexWriter.java
* (edit) 
phoenix-core/src/it/java/org/apache/phoenix/end2end/index/GlobalIndexCheckerIT.java
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/hbase/index/write/TrackingParallelWriterIndexCommitter.java
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/hbase/index/write/IndexCommitter.java
* (edit) 
phoenix-core/src/test/java/org/apache/phoenix/hbase/index/write/TestIndexWriter.java


> Able to write indexed value to data table without writing to index table
> ------------------------------------------------------------------------
>
>                 Key: PHOENIX-5515
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5515
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.14.3
>            Reporter: Vincent Poon
>            Assignee: Kadir OZDEMIR
>            Priority: Major
>             Fix For: 4.15.0, 5.1.0
>
>         Attachments: PHOENIX-5515.master.001.patch, 
> PHOENIX-5515.master.002.patch
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> Using the 4.14.3 client, it still seems the IndexFailurePolicy is still 
> kicking in, which disables the index on write failure.  This means that while 
> the index is in 'disabled' state, writes to the data table can happen without 
> any writes to the index table.  While in theory this might be ok since the 
> rebuilder should eventually kick in and rebuild from the disable_timestamp, 
> this breaks the new indexing design invariant that there should be no data 
> table rows without a corresponding index row (potentially unverified), so 
> this could potentially cause some unexpected behavior.
> Steps to repro:
> 1) Create data table
> 2) Create index table
> 3) "close_region" on index region from hbase shell
> 4) Upsert to data table
> Eventually after some number of retries, the index will get disabled, which 
> means any other client can write to the data table without writing to the 
> index table.



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

Reply via email to