Public signup for this instance is disabled. Go to our Self serve sign up page to request an account. Report potential security issues privately

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