You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/11 23:57:00 UTC

[jira] [Closed] (HBASE-2839) Fast find of all that has been modified since timestamp X

     [ https://issues.apache.org/jira/browse/HBASE-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Kyle Purtell closed HBASE-2839.
--------------------------------------

> Fast find of all that has been modified since timestamp X
> ---------------------------------------------------------
>
>                 Key: HBASE-2839
>                 URL: https://issues.apache.org/jira/browse/HBASE-2839
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Michael Stack
>            Priority: Major
>
> 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?



--
This message was sent by Atlassian Jira
(v8.20.7#820007)