accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1000) support compare and set
Date Wed, 05 Jun 2013 14:40:20 GMT


Sean Busbey commented on ACCUMULO-1000:

We should definitely allow passing of auths, so -1 to #2.

#4 would be consistent with what we do for the rest of the Mutation API, which I like, but
I agree that it smells of confused users down the road.

#1 seems most supportable, since it makes clear that you're only checking what you're allowed
to see. As a bonus a change from required -> optional would be non-breaking, but not vice-versa,
so we could change to #4 or #3 down the line if operational use finds them compelling.
> support compare and set
> -----------------------
>                 Key: ACCUMULO-1000
>                 URL:
>             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:

View raw message