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, 19 Sep 2014 02:39:33 GMT

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

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

>From your explanation, it seems the system namespace does probably make the most sense,
especially if the table is only written to by the system user, and the table is primarily
used internally. I don't see a problem with creating it on upgrade/init... if it's built-in,
it's built-in. It can stay offline, though, if the replication system is turned off.

(Note: I also agree that the tracer credentials are currently sub-par, but hopefully it'll
make more sense in the future, if we ever integrate with a standard tracing library, and the
trace table is just one possible sink for that tracing library, because it really will be
external to Accumulo at that point...)

> 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: Bug
>          Components: replication
>            Reporter: Christopher Tubbs
>            Assignee: Josh Elser
>             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