Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8069010920 for ; Thu, 6 Jun 2013 00:12:22 +0000 (UTC) Received: (qmail 18988 invoked by uid 500); 6 Jun 2013 00:12:21 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 18930 invoked by uid 500); 6 Jun 2013 00:12:21 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 18809 invoked by uid 99); 6 Jun 2013 00:12:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Jun 2013 00:12:21 +0000 Date: Thu, 6 Jun 2013 00:12:21 +0000 (UTC) From: "Keith Turner (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-1000) support compare and set MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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