Bulk Operation

KUDU-430 C++ client: propagate timestamp for write operations

KUDU-430 Document Consistency Semantics

KUDU-430 Add a way to set ReplicaSelection to the java client

KUDU-430 Add a new read mode to perform bounded staleness snapshot reads

KUDU-430 Handle snapshot reads that might block indefinitely

KUDU-430 Document/Implement read-your-writes for Impala/Spark etc.

KUDU-430 Propagate timestamps for scans

KUDU-430 Setting snapshot timestamp to last propagated timestamp should include prior writes

KUDU-430 On reads at a snapshot that touch multiple tablets, without the user setting a timestamp, use the timestamp from the first server for following scans

KUDU-430 For snapshot read correctness, enforce simple form of leader leases

KUDU-430 Avoid holding RPC handler threads on replicas that are part of a degraded tablet

KUDU-430 Proper safe time advancement by leaders and replicas

KUDU-430 Consistency for alter table operations

KUDU-430 Cryptographically sign the operation timestamps returned on server responses.

KUDU-430 Specification for expected semantics and client modes

KUDU-430 c++ client: implement HT timestamp propagation via scan tokens

KUDU-430 Snapshot scans should only refuse scans with timestamps whose value is > now+error

KUDU-430 Create an integration test that performs writes with multiple consistency modes

KUDU-430 Support for encoding REINSERT

KUDU-430 Add a mock clock to HybridClock

KUDU-430 Timestamps are being ignored in bootstrap

KUDU-430 Make replica/replayed transactions take the same timestamp as the original ones