[PHOENIX-5233] Read-your-own writes causes incorrect visibility with transactional tables (with Omid).

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.14.1
• Fix Version/s: 4.15.0, 5.1.0
• Assignee: Yoni Gottesman
• Reporter: Lars Hofhansl
• Created: 09/Apr/19 09:09
• Updated: 21/Dec/19 00:54
• Resolved: 13/May/19 00:20

Description

(copied from my last comment on PHOENIX-5090)
Steps to reproduce (with Omid):

1. !autocommit off
2. create table test (pk1 integer not null, pk2 integer not null, pk3 integer not null, v1 float, v2 float, v3 integer CONSTRAINT pk PRIMARY KEY (pk1, pk2, pk3)) DISABLE_WAL=true, TRANSACTIONAL=true;
3. upsert into test values(rand()*10000000, rand()*10000000, rand()*10000000, rand(), rand(), rand()*1000000);
4. upsert into test select rand()*10000000, rand()*10000000, rand()*10000000, rand(), rand(), rand()*1000000 from test;
5. select count(*) from test; – this will cause uncommitted data to sent to the server.
6. Goto #4 a few time (until you inserted 131072 rows)
7. !commit

In a separate sqlline session just repeat after the commit was issued in the other session.

• select count(*) from test;

You'll see that number will change until it finally settles.

Issue Links

• depends upon: PHOENIX-5225 Update Omid to 1.0.1
• is related to: OMID-144 Read from commit table doesnt remove checkpoint bits
• is related to: PHOENIX-5090 Allow transactional writes without buffering the entire transaction on the client.