hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5993) Add a no-read Append
Date Wed, 30 May 2012 08:15:24 GMT

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

Lars Hofhansl commented on HBASE-5993:
--------------------------------------

Honestly, I still do not understand what Jacques is proposing. In order to append to something
you'd have to read that something first. HBase has no in place updates (for a good reason).
So one could:
# Replace the KV if it is still in the memstore.
# Store incremental changes (somewhere?) and combine upon read from HBase.

                
> Add a no-read Append
> --------------------
>
>                 Key: HBASE-5993
>                 URL: https://issues.apache.org/jira/browse/HBASE-5993
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>    Affects Versions: 0.94.0
>            Reporter: Jacques
>            Priority: Critical
>
> HBASE-4102 added an atomic append.  For high performance situations, it would be helpful
to be able to do appends that don't actually require a read of the existing value.  This would
be useful in building a growing set of values.  Our original use case was for implementing
a form of search in HBase where a cell would contain a list of document ids associated with
a particular keyword for search.  However it seems like it would also be useful to provide
substantial performance improvements for most Append scenarios.
> Within the client API, the simplest way to implement this would be to leverage the existing
Append api.  If the Append is marked as setReturnResults(false), use this code path.  If result
return is requested, use the existing Append implementation.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message