accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-2705) Figure out internal authentication
Date Mon, 21 Apr 2014 19:00:16 GMT


Josh Elser commented on ACCUMULO-2705:

bq. If it simplifies things, why not create it on upgrade/init and leave it unused?

Hypothetically, it does. I spent a few hours trying to do this on Friday, actually. When you
circumvent the APIs and manually create a table, you have to use a fixed table ID. You then
*also* have to make sure that operations against {{accumulo.metadata}} still "consider" it
a table. After bashing my head against it for a few hours, I gave up. While there is the simplicity
argument for creating the table up front, there is the implementation complexity of having
a table which doesn't follow the same "rules" as every other table (with nothing being special
about said table).

> Figure out internal authentication
> ----------------------------------
>                 Key: ACCUMULO-2705
>                 URL:
>             Project: Accumulo
>          Issue Type: Sub-task
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.7.0
> When creating a table to use for storing replication "bookkeeping", I found that the
internal !SYSTEM user doesn't have the ability to create a table. Should it?
> Without this, the user would have to create/configure a custom local user account with
proper credentials to read/write the replication table as well as persist this in accumulo-site.xml.
My first impression is that this is excessive waste because the usage is purely within the
tablet server already -- need to try to figure out if there's a reason that !SYSTEM shouldn't
be allowed to create tables.

This message was sent by Atlassian JIRA

View raw message