Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-9905

Enable using seqId as timestamp

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Closed
    • Major
    • Resolution: Abandoned
    • None
    • None
    • None
    • None

    Description

      This has been discussed previously, and Lars H. was mentioning an idea from the client to declare whether timestamps are used or not explicitly.

      The problem is that, for data models not using timestamps, we are still relying on clocks to order the updates. Clock skew, same milisecond puts after deletes, etc can cause unexpected behavior and data not being visible.

      We should have a table descriptor / family property, which would declare that the data model does not use timestamps. Then we can populate this dimension with the seqId, so that global ordering of edits are not effected by wall clock.

      For example, META will use this.

      Once we have something like this, we can think of making it default for new tables, so that the unknowing user will not shoot herself in the foot.

      Attachments

        1. HBaseTimespaceGeneratorProposal.pdf
          97 kB
          Andrey Stepachev

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            enis Enis Soztutar
            Votes:
            0 Vote for this issue
            Watchers:
            22 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment