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 1D0E71867F for ; Thu, 30 Apr 2015 21:29:09 +0000 (UTC) Received: (qmail 20385 invoked by uid 500); 30 Apr 2015 21:29:09 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 20322 invoked by uid 500); 30 Apr 2015 21:29:09 -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 20301 invoked by uid 99); 30 Apr 2015 21:29:08 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Apr 2015 21:29:08 +0000 Date: Thu, 30 Apr 2015 21:29:08 +0000 (UTC) From: "Josh Elser (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-3604) connector.instanceOperations().setSystemProperty(String,String) returns silently for non-changeable ZK Property's 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-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14522301#comment-14522301 ] Josh Elser commented on ACCUMULO-3604: -------------------------------------- bq. Is logging the exception necessary if we're throwing it? I think I recommended he do this at the Hackathon. We aren't guaranteed to see a thrown exception on the server. It is not at warn because, like you said, it's not necessarily an issue to worry about. Being able to catch this error being spammed at the debug level seemed appropriate though. > connector.instanceOperations().setSystemProperty(String,String) returns silently for non-changeable ZK Property's > ----------------------------------------------------------------------------------------------------------------- > > Key: ACCUMULO-3604 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3604 > Project: Accumulo > Issue Type: Bug > Components: master > Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2 > Reporter: Josh Elser > Assignee: Jeffrey S Schwartz > Labels: newbie, summit2015 > Fix For: 1.5.3, 1.6.3, 1.8.0, 1.7.1 > > Attachments: ACCUMULO-3604.patch > > > Only a subset of the configuration {{Property}}'s in Accumulo are modifiable via ZooKeeper (defined by {{Property.isValidZooProperty}}). > {{connector.instanceOperations().setProperty(String,String)}} updates the provided property name with the given value in ZooKeeper. The thing that is never mentioned is that only a subset of the properties in Accumulo are allowed to be overriden in ZooKeeper. Furthermore, the user receives no indication that their call failed. > The Javadoc on {{setSystemProperty(String,String)}} should be updated to inform the users that only some properties can be changed by this method, and some information should be returned back to the user to let them know that their call did not succeed (likely an Exception). -- This message was sent by Atlassian JIRA (v6.3.4#6332)