[
https://issues.apache.org/jira/browse/HBASE-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692678#comment-13692678
]
Andrew Purtell commented on HBASE-3787:
---------------------------------------
bq. accumulo's acl's are in sort order
Accumulo has visibility expressions, not ACLs.
Considering the visibility expression part of the KV was the cause of the data
inflation discussed in Himanshu's proposal on HBASE-6222.
bq. We can have system level tags that are sortable vs user level tags, or a
boolean per tag indicating whether the value is sortable.
How do we distinguish system level tags? I want my coprocessor to have system
level tags. It will be registered dynamically on a per table basis.
So if there's a boolean per tag, then the comparator is skipping a range,
checking a byte, including a range, skipping another range, testing another
byte, and so on.
I don't think tags should be considered by KeyValue or Cell comparators at all.
> Increment is non-idempotent but client retries RPC
> --------------------------------------------------
>
> Key: HBASE-3787
> URL: https://issues.apache.org/jira/browse/HBASE-3787
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.94.4, 0.95.2
> Reporter: dhruba borthakur
> Assignee: Sergey Shelukhin
> Priority: Critical
> Fix For: 0.95.2
>
> Attachments: HBASE-3787-partial.patch, HBASE-3787-v0.patch,
> HBASE-3787-v1.patch, HBASE-3787-v2.patch, HBASE-3787-v3.patch,
> HBASE-3787-v4.patch, HBASE-3787-v5.patch, HBASE-3787-v5.patch
>
>
> The HTable.increment() operation is non-idempotent. The client retries the
> increment RPC a few times (as specified by configuration) before throwing an
> error to the application. This makes it possible that the same increment call
> be applied twice at the server.
> For increment operations, is it better to use
> HConnectionManager.getRegionServerWithoutRetries()? Another option would be
> to enhance the IPC module to make the RPC server correctly identify if the
> RPC is a retry attempt and handle accordingly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
