[PHOENIX-5090] Allow transactional writes without buffering the entire transaction on the client.

• Type: Wish
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.15.0, 5.1.0
• Assignee: Lars Hofhansl
• Reporter: Lars Hofhansl
• Created: 04/Jan/19 18:08
• Updated: 21/Dec/19 00:56
• Resolved: 13/May/19 00:25

Description

Currently it is not possible execute transactions in Phoenix that are too large to be buffered entirely on the client.

Both Tephra and Omid support writing uncommitted data to HBase immediately and at full speed. The client still needs to keep tracks of the rows changes for:

1. Conflict detection
2. (for Omid) writing the shadow cells

I'd like to do some brainstorming here.

• It should always be enough to only hold on to the changed rows (and columns?) only for conflict resolution and free the rest from the client as soon as the uncommitted data is written to HBase.
• For the shadows cells we need only keep the rows changed, right?
• There are situations where we can avoid the client site buffering entirely (perhaps only for Tephra) when we declare a table or upsert not to participate in conflict resolution.

tdsilva, ohads, yonigo, jamestaylor, vincentpoon, more, better ideas?

Issue Links

• is related to: PHOENIX-5082 Observations about the Phoenix-Omid integration
• relates to: PHOENIX-5233 Read-your-own writes causes incorrect visibility with transactional tables (with Omid).