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 Thu, 06 Jun 2013 01:57:19 GMT


Sean Busbey commented on ACCUMULO-1000:

re: Column and Test Objects

I liked the simplicity of vanilla methods to add conditions to the ConditionalMutation. This
might just be my bias against Object creation in Java.

the unwrapped version has the advantage of looking more like other methods used in Mutation.

If you do go down this route:

bq. That would be nice, but what about constructors? Absence() and Equality(byte[] val) are
different constructors, suggestions?

* Change Column to Cell, make val another optional argument.
* Make the docs expressly say that not setting an optional argument means "any". 
* Make Test enums have only noargs constructor.
* Make the entire correctness check in the Test instance, so all of them get the entire Cell
* Either allow Absence checks that go to the value level or document that it will ignore any
value in the Cell.

On that last bit, I'm in favor of the former. But maybe then "AbsenceTest" becomes "NonEqualityTest"
> 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