[ 
https://issues.apache.org/jira/browse/HBASE-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926538#action_12926538
 ] 

HBase Review Board commented on HBASE-3162:
-------------------------------------------

Message from: "Jonathan Gray" <[email protected]>


bq.  On 2010-10-29 21:19:11, Ryan Rawson wrote:
bq.  > trunk/src/main/java/org/apache/hadoop/hbase/client/Increment.java, line 
274
bq.  > <http://review.cloudera.org/r/1132/diff/1/?file=16260#file16260line274>
bq.  >
bq.  >     technically Increment.java has never shipped in a published version 
of HBase so we wont need to bump any version numbers I think.

+1


- Jonathan


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://review.cloudera.org/r/1132/#review1720
-----------------------------------------------------------





> Add TimeRange support into Increment to optimize for counters that are 
> partitioned on time
> ------------------------------------------------------------------------------------------
>
>                 Key: HBASE-3162
>                 URL: https://issues.apache.org/jira/browse/HBASE-3162
>             Project: HBase
>          Issue Type: Improvement
>          Components: client, regionserver
>    Affects Versions: 0.90.0
>            Reporter: Jonathan Gray
>            Assignee: Jonathan Gray
>            Priority: Minor
>             Fix For: 0.90.0
>
>         Attachments: HBASE-3162-v1.patch
>
>
> In many use cases of increments, a given counter is only incremented during a 
> specific window of time (ie. the counters are partitioned/sharded by time).
> With this kind of schema, you are constantly creating new counters.  When a 
> new counter is "created" (incremented the first time) you will always end up 
> looking at a block from every file in the region because no previous value 
> will exist.  However, with the new TimeRange optimizations that skip files if 
> they don't contain values of the TimeRange you're interested in, we could 
> utilize that information to optimize the Get within the increment.
> This would be optional and an addition to the Increment class.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to