Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-10070 HBase read high-availability using timeline-consistent region replicas
  3. HBASE-11634

Disallow non-atomic update operations when TIMELINE consistency is enabled

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Later
    • Affects Version/s: 0.99.0, hbase-10070
    • Fix Version/s: None
    • Component/s: Client, Usability
    • Labels:
      None

      Description

      Something to consider for the HBASE-10070 line of changes. When a client reads a timeline consistent view of data, read-update-write operations are potentially destructive. When a client is accepting TIMELINE reads, we should only allow server-side atomic update operations.

      In a future state, we could offer a CRDT-based data type to further extend the set of write operations that are guaranteed safe under this consistency model.

      I may not have the semantics of the new client API correct, but this is the idea: do what we can to protect users from the major dangers of this relaxed consistency model.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              ndimiduk Nick Dimiduk
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: