hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19427) Add TimeRange support into Append to optimize for counters
Date Mon, 11 Dec 2017 17:38:05 GMT

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

stack commented on HBASE-19427:
-------------------------------

How does this work [~chia7712] ? If we offer a TimeRange that does not include the last Append,
then the Append will start over overwriting what was there previous? Should we have this same
facility in Increment and CheckAndMutate? (Looks like Increment already has this -- so if
timerange does not include last increment, the increment starts over?)

Patch LGTM.



> Add TimeRange support into Append to optimize for counters
> ----------------------------------------------------------
>
>                 Key: HBASE-19427
>                 URL: https://issues.apache.org/jira/browse/HBASE-19427
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>             Fix For: 2.0.0-beta-1
>
>         Attachments: HBASE-19427.v0.patch, HBASE-19427.v1.patch
>
>
> The time range in Increment is used to optimize the Get operation. This issue try to
port the feature from Increment to Append.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message