accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2016) Default namespace should not allow any configurations
Date Mon, 16 Dec 2013 18:49:09 GMT

    [ 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)

Mime
View raw message