[
https://issues.apache.org/jira/browse/ACCUMULO-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13670515#comment-13670515
]
Sean Busbey commented on ACCUMULO-1000:
---------------------------------------
>From the mailing list:
{quote}
In the design document I suggested a method called putCondition() and if
the value was null, thats mean that the user expected it to be absent. I
don't really like that API for specifying expected absence.
{quote}
Could we do this as an additional method instead? relying on null for special
API behavior smells like it'll lead to unexpected behavior if users mess up.
{code}
/**
* Specify that a given cell must not exist
*/
void putConditionAbsent(CharSequence cf, CharSequence cq, ColumnVisibility
cv) {}
{code}
And then putCondition can assert all non-null arguments.
> support compare and set
> -----------------------
>
> Key: ACCUMULO-1000
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1000
> Project: Accumulo
> Issue Type: New Feature
> Components: client, tserver
> Reporter: Keith Turner
> Assignee: Keith Turner
> Fix For: 1.6.0
>
> Attachments: ACCUMULO-1000-proposal-01.html,
> ACCUMULO-1000-proposal-01.txt
>
>
> Add support to mutation for compare and set operations. This would allow
> user to specify that a row must contain certain data for a mutation to be
> applied.
--
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
