You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jonathan Gray (JIRA)" <ji...@apache.org> on 2010/06/23 10:00:50 UTC
[jira] Created: (HBASE-2776) Track and persist max/min timestamp
per StoreFile in HFile meta block
Track and persist max/min timestamp per StoreFile in HFile meta block
---------------------------------------------------------------------
Key: HBASE-2776
URL: https://issues.apache.org/jira/browse/HBASE-2776
Project: HBase
Issue Type: New Feature
Components: io, regionserver
Reporter: Jonathan Gray
This is an idea to help optimize cases where a user asks for a specific TimeStamp or TimeRange in their query.
If specifying a TimeRange, we are unable to use any kind of bloom to determine whether we need to open every file or not. If we knew the max/min timestamps in each file, we could use that information to prevent opening files we know do not contain any versions from the query's TimeRange.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HBASE-2776) Track and persist max/min timestamp
per StoreFile in HFile meta block
Posted by "Jonathan Gray (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Gray resolved HBASE-2776.
----------------------------------
Resolution: Duplicate
Yes
> Track and persist max/min timestamp per StoreFile in HFile meta block
> ---------------------------------------------------------------------
>
> Key: HBASE-2776
> URL: https://issues.apache.org/jira/browse/HBASE-2776
> Project: HBase
> Issue Type: New Feature
> Components: io, regionserver
> Reporter: Jonathan Gray
>
> This is an idea to help optimize cases where a user asks for a specific TimeStamp or TimeRange in their query.
> If specifying a TimeRange, we are unable to use any kind of bloom to determine whether we need to open every file or not. If we knew the max/min timestamps in each file, we could use that information to prevent opening files we know do not contain any versions from the query's TimeRange.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-2776) Track and persist max/min timestamp
per StoreFile in HFile meta block
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881607#action_12881607 ]
Todd Lipcon commented on HBASE-2776:
------------------------------------
Dup HBASE-2265?
> Track and persist max/min timestamp per StoreFile in HFile meta block
> ---------------------------------------------------------------------
>
> Key: HBASE-2776
> URL: https://issues.apache.org/jira/browse/HBASE-2776
> Project: HBase
> Issue Type: New Feature
> Components: io, regionserver
> Reporter: Jonathan Gray
>
> This is an idea to help optimize cases where a user asks for a specific TimeStamp or TimeRange in their query.
> If specifying a TimeRange, we are unable to use any kind of bloom to determine whether we need to open every file or not. If we knew the max/min timestamps in each file, we could use that information to prevent opening files we know do not contain any versions from the query's TimeRange.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.