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

Client promises about timestamps

    XMLWordPrintableJSON

Details

    • Brainstorming
    • Status: Closed
    • Minor
    • Resolution: Won't Fix
    • None
    • None
    • None
    • None

    Description

      This is to start a discussion about timestamp promises declared per table of CF.
      For example if a client promises only monotonically increasing timestamps (or no custom set timestamps) and VERSIONS=1, we can aggressively and easily remove old versions of the same row/fam/col from the memstore before we flush, just by supplying a comparator that ignores the timestamp (i.e. two KV just differing by TS would be considered equal).
      That would increase the performance of counters significantly.

      Attachments

        1. 10247-do-not-try-may-eat-your-first-born-v2.txt
          19 kB
          Lars Hofhansl
        2. 10247.txt
          11 kB
          Lars Hofhansl

        Issue Links

          is related to

          New Feature - A new feature of the product, which has yet to be developed. HBASE-14070 Hybrid Logical Clocks for HBase

          • Major - Major loss of function.
          • Reopened
          relates to

          New Feature - A new feature of the product, which has yet to be developed. HBASE-9905 Enable using seqId as timestamp

          • Major - Major loss of function.
          • Closed

          Umbrella - An overarching type made of sub-tasks HBASE-10856 Prep for 1.0

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              larsh Lars Hofhansl
              Votes:
              0 Vote for this issue
              Watchers:
              20 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: