accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1000) support compare and set
Date Thu, 06 Jun 2013 03:54:19 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676650#comment-13676650
] 

Keith Turner commented on ACCUMULO-1000:
----------------------------------------

bq. Ah, yeah that makes sense now. Presumably an IllegalArgumentException?

When a batch of conditional mutations is passed to the conditional writer, can not throw an
exception.  Need to know the status of each one.  I am thinking of adding something to the
status enum, just not sure what to call the enum.

bq. Can you put it up on the gitchubs or bitbucket?

https://github.com/keith-turner/ACCUMULO-1000

[~busbey], I like the Cell proposal.  I also agree w/ your arguments for not using it.

bq.  This might just be my bias against Object creation in Java.

Thats a good bias to have (if only there were some safe way to allocate objects on the stack).
 Normally I would agree w/ this, but I am thinking in this case the operation (lock row on
server side, read, maybe update) is so expensive that it possibly dwarfs this concern.  However
in the case where data is cached in the tserver its not as expensive.

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

Agreed, consistency is very important.  For me this is the main argument for not using the
Cell+Test design.  Changing the API for mutation is not really an option.   

[~bills] I just fully understood the significance of your earlier comment w.r.t API.  Users
will be able to do any check they like using iterators.  Therefore we do not need to anticipate
future mutation conditions besides equality and presence.
                
> 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

Mime
View raw message