accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3147) Replication table should be user-controlled or live in accumulo namespace
Date Fri, 31 Oct 2014 19:56:34 GMT

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

Christopher Tubbs commented on ACCUMULO-3147:
---------------------------------------------

I'm not sure how that helps anything. The main intent here is that the table's role as a system-managed
table, with clear expectations with regard to user permissions and naming conflicts, be well
defined. Storing something in ZooKeeper to identify the table does not clarify anything for
users, with regard to their expectations for this table. Unless... you're proposing something
like option 3 above, but instead of specifying credentials, you'd want to specify the table
name?

I have a patch in the works that gets us to option 1, which I hope will be ready tomorrow.

> Replication table should be user-controlled or live in accumulo namespace
> -------------------------------------------------------------------------
>
>                 Key: ACCUMULO-3147
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3147
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: replication
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>            Priority: Blocker
>             Fix For: 1.7.0
>
>
> At present, it looks like the replication table is managed by/written to by the system
user, yet the table lives in the default namespace, which is where user tables live.
> This appears to violate the namespace model of segregating system tables from user tables.
> There's a few options for resolution:
> # Move the replication table into the reserved accumulo system namespace (there's some
complication with this, because the system namespace is currently static, and the replication
table may be created at any time; additionally, if users are expected to interact with this
table... and I'm not sure if they are at all, the system namespace is probably not appropriate).
> # Create an additional reserved system namespace for replication (my least preferred
option).
> # Use user credentials to manage/write to this table, rather than the system user (this
is what the tracer/trace table does, and this is my preferred solution.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message