accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1000) support compare and set
Date Sat, 08 Jun 2013 01:22:20 GMT


Keith Turner commented on ACCUMULO-1000:

bq. I would like to see the IteratorOptions pushed down to the ConditionalMutations, rather
than put on the ConditionalWriter.


bq. I would also like to see an explicit addCondition(Condition) 

I think pushing the iterator option down to the condition necessitates a Condition object,
otherwise the overloading would be completely insane.  So I did this on github. I created
a [Condition class|]
where visibility, timestamp, value, and iterators are optional.  If the value is not set,
then its expected to be absent.  I replaced all of the putCondition() methods with a single
addCondition() method (replacing the implementions of putCondition() w/ addCondition() and
then inlining the putCondition methods in eclipse made this so easy, much easier that typing
this explanation)
> 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