[KUDU-1841] Add a client write mode like AUTO_BACKGROUND_FLUSH + data dependencies

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: client
• Assignee: Unassigned
• Reporter: Mike Percy
• Created: 19/Jan/17 19:44
• Updated: 19/Jan/17 21:40

Description

After considering KUDU-1767, it is clear that we could provide a friendlier client mode for ingest use cases. I think a useful one would be a mode that "feels" like AUTO_BACKGROUND_FLUSH - with only a loose idea of ordering to maximize throughput and no requirement for an explicit flush - but that would also implement a "mutex" for each unique key being written such that writes to a given row always occur in order relative to later writes to the same row, as seen by the client session and the data store.

Such a mode might also be looked at as providing "eventual consistency" because after quiescing writes and reading the latest values it would appear that the data was written in client session order.

Issue Links

• is related to: KUDU-1767 Reordering of client operations from the same KuduSession is possible