[
https://issues.apache.org/jira/browse/PHOENIX-4980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16655882#comment-16655882
]
Abhishek Talluri edited comment on PHOENIX-4980 at 10/18/18 9:24 PM:
---------------------------------------------------------------------
No, I made sure that i had the table dropped when that mismatch occurs and
recreate the table and index for next test cycle. Also, after you observe a
mismatch and do a delete from table_name, if the count is zero that is
basically the count from the table rather than the index, there are records
still lying around in the index which i was able to verify by scanning the raw
hbase index table or by forcing the count(*) query to use index rather than the
table
was (Author: [email protected]):
No, I made sure that i had the table dropped when that mismatch occurs and
recreate the table and index for next test cycle.
> Mismatch in row counts between data and index tables while multiple clients
> try to upsert data
> ----------------------------------------------------------------------------------------------
>
> Key: PHOENIX-4980
> URL: https://issues.apache.org/jira/browse/PHOENIX-4980
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.14.0
> Reporter: Abhishek Talluri
> Priority: Major
> Labels: LocalIndex, globalMutableSecondaryIndex, secondaryIndex
> Attachments: TestSecIndex.java
>
>
> Phoenix table has A,B,C,D,E as its columns and A as the primary key for the
> table.
> CREATE TABLE TEST (A VARCHAR NOT NULL PRIMARY KEY, B VARCHAR, C VARCHAR, D
> VARCHAR , E VARCHAR);
> Global index is built on D & E
> CREATE INDEX TEST_IND on TEST (D,E);
> Client 1 updates A,B,C whereas client 2 updates A,B,D,E
> I used phoenix 5.14.2-1.cdh5.14.2.p0.3 parcel to test this issue. Ran with
> two threads that load data using upserts reading from the csv file. Within 10
> iterations, i could observe the difference in the row counts between data
> table and index table. Attaching the code used to test this behavior. This
> issue also exists in both Global and Local indexes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
