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 BC2E4104C2 for ; Wed, 20 Nov 2013 16:29:43 +0000 (UTC) Received: (qmail 72980 invoked by uid 500); 20 Nov 2013 16:29:39 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 72782 invoked by uid 500); 20 Nov 2013 16:29:36 -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 72658 invoked by uid 99); 20 Nov 2013 16:29:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Nov 2013 16:29:35 +0000 Date: Wed, 20 Nov 2013 16:29:35 +0000 (UTC) From: "Keith Turner (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-1909) Adding list of conditions to conditional mutation is cumbersome. 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-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827820#comment-13827820 ] Keith Turner commented on ACCUMULO-1909: ---------------------------------------- bq. Why not just issue a WARN and act as a pass-through when there are no conditions present? Two reasons : # The users intent was probably to have a condition, not having one indicates an error in their code. If warning is logged and no one see its then this bug goes unnoticed. # The conditional writer is an inefficient way to write mutations relative to the batch writer. > Adding list of conditions to conditional mutation is cumbersome. > ---------------------------------------------------------------- > > Key: ACCUMULO-1909 > URL: https://issues.apache.org/jira/browse/ACCUMULO-1909 > Project: Accumulo > Issue Type: Sub-task > Components: client, tserver > Reporter: Keith Turner > Fix For: 1.6.0 > > > The conditional mutation constructor requires that a user pass in at least one condition. For cases where I have a list of data that I want to create conditions from I have found this to be very cumbersome writing code like the following. > {code:java} > List cdata = ...; > ConditionalMutation cm = null; > for(String s : cdata){ > Condition condition = createCondition(s); > if(cm == null) > cm = new ConditionalMutation(row, condition) > else > cm.addCondition(condition); > } > {code} -- This message was sent by Atlassian JIRA (v6.1#6144)