HBase
  1. HBase
  2. HBASE-2839

Fast find of all that has been modified since timestamp X

    Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Not a Problem
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      This request has come up a few times now (http://search-hadoop.com/m/jUPWLpi9go and during a conversation at hadoop summit). Building a secondary index keyed by time seems just wrong. Can't we do better? A scan-in-parallel might help – see hbase-1935. Other ideas?

        Issue Links

          Activity

          stack created issue -
          Jeff Hammerbacher made changes -
          Field Original Value New Value
          Link This issue is related to HBASE-1935 [ HBASE-1935 ]
          Andrew Purtell made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Not a Problem [ 8 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              stack
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development