Details

    • Type: New Feature
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: M4
    • Fix Version/s: None
    • Component/s: client, tablet, tserver
    • Labels:
    • Target Version/s:

      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

          1.
          Make replica/replayed transactions take the same timestamp as the original ones Sub-task Resolved David Alves
          2.
          Timestamps are being ignored in bootstrap Sub-task Resolved David Alves
          3.
          Add a mock clock to HybridClock Sub-task Resolved David Alves
          4.
          Snapshot scans should only refuse scans with timestamps whose value is > now+error Sub-task Resolved Todd Lipcon
          5.
          Setting snapshot timestamp to last propagated timestamp should include prior writes Sub-task Resolved Unassigned
          6.
          Proper safe time advancement by leaders and replicas Sub-task Resolved David Alves
          7.
          Support for encoding REINSERT Sub-task Resolved David Alves
          8.
          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 Sub-task Resolved Alexey Serbin
          9.
          Propagate timestamps for scans Sub-task Resolved Alexey Serbin
          10.
          Avoid holding RPC handler threads on replicas that are part of a degraded tablet Sub-task Resolved David Alves
          11.
          Add a way to set ReplicaSelection to the java client Sub-task Resolved Jean-Daniel Cryans
          12.
          c++ client: implement HT timestamp propagation via scan tokens Sub-task Resolved Alexey Serbin
          13.
          C++ client: propagate timestamp for write operations Sub-task Resolved Alexey Serbin
          14.
          Handle snapshot reads that might block indefinitely Sub-task Closed David Alves
          15.
          Create an integration test that performs writes with multiple consistency modes Sub-task Resolved David Alves
          16.
          For snapshot read correctness, enforce simple form of leader leases Sub-task Open David Alves
          17.
          Specification for expected semantics and client modes Sub-task Open David Alves
          18.
          Add a new read mode to perform bounded staleness snapshot reads Sub-task Resolved Hao Hao
          19.
          Document Consistency Semantics Sub-task Resolved Todd Lipcon
          20.
          Document/Implement read-your-writes for Impala/Spark etc. Sub-task Open David Alves
          21.
          Consistency for alter table operations Sub-task Open Unassigned
          22.
          Cryptographically sign the operation timestamps returned on server responses. Sub-task Open Unassigned

            Activity

              People

              • Assignee:
                dralves David Alves
                Reporter:
                tlipcon Todd Lipcon
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated: