accumulo-notifications mailing list archives

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

    [ https://issues.apache.org/jira/browse/ACCUMULO-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849736#comment-13849736
] 

John Vines commented on ACCUMULO-2016:
--------------------------------------

By default, no one has that permission, but root can grant it to itself or others. I like
your train of thought, in that we shouldn't wedge in this special casing into the code while
we have a functional deterrent. So if someone really wants to do it, they can.

> 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