[
https://issues.apache.org/jira/browse/ACCUMULO-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676528#comment-13676528
]
Keith Turner commented on ACCUMULO-1000:
----------------------------------------
[~billie.rinaldi] and [~busbey] you both made comments about auths and vis,
did the example w/ auth "A" and col vis "B" address your concerns? Want to
make sure we are not talking past each other.
bq. #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-vers
good point. I am going to go w/ that option for now in my prototype. If
anyone wants to see my client side prototype let me know. Once the discussion
settles for a bit I will post another revision of the design doc.
> 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
