Details
-
New Feature
-
Status: Open
-
Major
-
Resolution: Unresolved
-
M4
-
None
Description
This ticket tracks consistency/isolation work for 1.2.
Scope Doc: https://docs.google.com/document/d/1EaKlJyQdMBz6G-Xn5uktY-d_x0uRmjMCrDGP5rZ7AoI/edit#
The sub-tasks that don't target 1.2 will likely be moved somewhere else, or promoted to tasks once this ticket is done, but for now it's handy to have a single view of all the remaining work
Attachments
Issue Links
- contains
-
KUDU-796 New leaders should not allow "up to date" reads until they've committed everything from previous terms
- Resolved
- is blocked by
-
KUDU-568 Exactly-once semantics on writes
- Resolved
-
KUDU-420 c++ client: implement HT timestamp propagation via scan tokens
- Resolved
-
KUDU-371 major delta compaction should generate UNDOs
- Resolved
-
KUDU-132 Integrate UNDOS in delta compaction
- Resolved
-
KUDU-236 GC tablet history
- Resolved
-
KUDU-235 Major delta compaction needs to spit out UNDO files
- Resolved
-
KUDU-1187 Full parity between clients regarding read/write modes
- Resolved
- is related to
-
KUDU-146 Deal with leap seconds
- Open
-
KUDU-1497 Full support for read-your-writes consistency
- Resolved
-
KUDU-1663 Clean-up in-code documentation for KuduScanner::ReadMode and KuduClient::GetLatestObservedTimestamp
- Resolved
- relates to
-
KUDU-1656 Scanner timeouts aren't retried when waiting on a transaction
- Resolved
-
KUDU-1697 Operations that have to wait for a certain time/condition to pass shouldn't block threads
- Open
1.
|
For snapshot read correctness, enforce simple form of leader leases | Open | David Alves | |
2.
|
Consistency for alter table operations | Open | Unassigned | |
3.
|
Cryptographically sign the operation timestamps returned on server responses. | Open | Unassigned |