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 Wed, 05 Jun 2013 22:17:19 GMT


Keith Turner commented on ACCUMULO-1000:

I was thinking about the following scenario w/ absence and auths.  In the case below, the
absence check will always succeed because the user is scanning for data w/ auth "A" and checking
that key w/ colvis "B" is absent.  The check is pointless, it must be a logic error in the
user code.   

   Connector conn;
   Authorizations auths = new Authorizations("A"); //auths used to read data
   ConditionalWriter cw = conn.createConditionalWriter(auths);

   ConditionalMutation cm = new ConditinalMutation("row1");
   cm.putConditionAbsent("name","last",B");   //this test will always succeed no matter whats
in the table

Only being able to write data that you can read is a separate case and is covered by a Constraint
that checks this case. 
> 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