You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Jaanai (JIRA)" <ji...@apache.org> on 2018/12/03 13:38:00 UTC

[jira] [Created] (PHOENIX-5055) Split the list of mutations into multiple batches probably cause correctness of index data

Jaanai created PHOENIX-5055:
-------------------------------

             Summary: Split the list of mutations into multiple batches probably cause correctness of index data
                 Key: PHOENIX-5055
                 URL: https://issues.apache.org/jira/browse/PHOENIX-5055
             Project: Phoenix
          Issue Type: Bug
    Affects Versions: 4.14.1, 5.0.0
            Reporter: Jaanai
            Assignee: Jaanai
             Fix For: 5.1.0


In order to get more performance, we split the list of mutations into multiple batches in MutationSate.  For one upsert SQL with some null values that will produce two type KeyValues(Put and DeleteColumn),  These KeyValues should have the same timestamp so that keep on an atomic operation for corresponding the row key.

 

Found incorrect indexed data for the index tables by sqlline.

!https://gw.alicdn.com/tfscom/TB1nSDqpxTpK1RjSZFGXXcHqFXa.png|width=665,height=400!

 

Running the following:
{code:java}
conn.createStatement().executeUpdate( "CREATE TABLE " + tableName + " (" + "A VARCHAR NOT NULL PRIMARY KEY," + "B VARCHAR," + "C VARCHAR," + "D VARCHAR) COLUMN_ENCODED_BYTES = 0"); 

conn.createStatement().executeUpdate("CREATE INDEX " + indexName + " on " + tableName + " (C) INCLUDE(D)"); 

conn.createStatement().executeUpdate("UPSERT INTO " + tableName + "(A,B,C,D) VALUES ('A2','B2','C2','D2')"); 
conn.createStatement().executeUpdate("UPSERT INTO " + tableName + "(A,B,C,D) VALUES ('A3','B3', 'C3', null)");
{code}
dump IndexMemStore:
{code:java}
hbase.index.covered.data.IndexMemStore(117): Inserting:\x01A3/0:D/1542190446218/DeleteColumn/vlen=0/seqid=0/value= phoenix.hbase.index.covered.data.IndexMemStore(133): Current kv state: phoenix.hbase.index.covered.data.IndexMemStore(135): KV: \x01A3/0:B/1542190446167/Put/vlen=2/seqid=5/value=B3 phoenix.hbase.index.covered.data.IndexMemStore(135): KV: \x01A3/0:C/1542190446167/Put/vlen=2/seqid=5/value=C3 phoenix.hbase.index.covered.data.IndexMemStore(135): KV: \x01A3/0:D/1542190446218/DeleteColumn/vlen=0/seqid=0/value= phoenix.hbase.index.covered.data.IndexMemStore(135): KV: \x01A3/0:_0/1542190446167/Put/vlen=1/seqid=5/value=x phoenix.hbase.index.covered.data.IndexMemStore(137): ========== END MemStore Dump ==================
{code}
 

The DeleteColumn's timestamp larger than other mutations.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)