[
https://issues.apache.org/jira/browse/HBASE-5993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285504#comment-13285504
]
Jieshan Bean commented on HBASE-5993:
-------------------------------------
One KeyValue will include 2 parts: The original value, and the appended value.
So if we append new value, just add this value into the "additional" part(Maybe
we can implement this by introducing a new KeyValue.Type). So we need to
combine the values. (@Jacques: Please correct me if I misunderstood anything).
I'm wondering whether it is really necessary.
> 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
