[
https://issues.apache.org/jira/browse/ACCUMULO-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139901#comment-14139901
]
Josh Elser commented on ACCUMULO-3147:
--------------------------------------
bq. It can stay offline, though, if the replication system is turned off.
Oh, that's not a bad idea. I hadn't thought of that myself. I'll try to take a
look at how the init/upgrade stuff works again to see if I can make it work. I
remember the first time around, I had a hard time figuring out how to correctly
"create" the table with Accumulo still offline (during init). Even though it
may seem goofy to a user to have that table magically show up when you enable
replication, it's certainly much easier to implement that (like I said before,
don't have to worry about init/upgrade cases at all).
> 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)
