[
https://issues.apache.org/jira/browse/ACCUMULO-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14191150#comment-14191150
]
Josh Elser commented on ACCUMULO-3147:
--------------------------------------
Was talking to [~billie.rinaldi] on the subject: what if, instead of having the
fully-qualified name for the replication table to read be a hard-coded thing,
we store the table ID (or whatever necessary identifier to get at the table) in
ZooKeeper. This would make any incompatibilities easier to handle down the
road, wouldn't fix us to what we currently think the replication table should
be called (or the namespace it should be in, etc etc) and would hopefully make
upgrade cases easier.
> 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)
