[
https://issues.apache.org/jira/browse/HBASE-5993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285335#comment-13285335
]
Jieshan Bean commented on HBASE-5993:
-------------------------------------
I'm not against this new feature, but anyway I don't think it's a good idea to
use this append API frequently w.r.t. one KeyValue. If one KeyValue need to
updated regularly, why not consdering a better key-schema?
e.g.
key-1, value
key-2, append-value1
key-3, append-value2
..........
then we can combine the results from client side.
Back to this improvement, the only advantage is combining the results from
server side is better than from client side. But we need to change the
read/scan logic. One seek may come together with another serveral seeks in
order to get the existing value and appended values,...
Maybe my understanding is not correct:)
> 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
