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 2BF0D105FC for ; Mon, 16 Dec 2013 18:49:10 +0000 (UTC) Received: (qmail 14758 invoked by uid 500); 16 Dec 2013 18:49:09 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 14714 invoked by uid 500); 16 Dec 2013 18:49: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 14653 invoked by uid 99); 16 Dec 2013 18:49:09 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Dec 2013 18:49:09 +0000 Date: Mon, 16 Dec 2013 18:49:09 +0000 (UTC) From: "Josh Elser (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-2016) Default namespace should not allow any configurations 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-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849579#comment-13849579 ] Josh Elser commented on ACCUMULO-2016: -------------------------------------- Who has permissions to even add an iterator to the default namespace? Only {{root}} I would assume? If it's only root, and we're thinking about"production-esque systems with multiple users properly corralled into their own namespaces, only the root user could even do this, which makes me think the risk of something adverse happening is small? I can't help but think if we enforce this limitation programmatically, we'll just end up creating/finding some use case which invalidates the assumption. > Default namespace should not allow any configurations > ----------------------------------------------------- > > Key: ACCUMULO-2016 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2016 > Project: Accumulo > Issue Type: Bug > Reporter: John Vines > Fix For: 1.6.0 > > > The bug with the default namespace having versioning iterators got me thinking. We shouldn't allow any iterators, or any special configurations, for the default namespace. I think it should be a special case namespace, and if people want configurations for all tables, they should all be in a namespace. -- This message was sent by Atlassian JIRA (v6.1.4#6159)