accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Newton (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (ACCUMULO-500) Need mechanism for init to work with empty /accumulo directory
Date Wed, 02 May 2012 15:28:52 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Eric Newton reassigned ACCUMULO-500:
------------------------------------

    Assignee: Eric Newton
    
> Need mechanism for init to work with empty /accumulo directory
> --------------------------------------------------------------
>
>                 Key: ACCUMULO-500
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-500
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: John Vines
>            Assignee: Eric Newton
>
> I don't know if this should be done for 1.4.1 or 1.5.0, but this is primarily to help
support ACCUMULO-404. In a secured installation, there is the assumption that the accumulo
user only has rwx access in the /accumulo directory and it's children. Unfortunately, Accumulo
only knows how to init with there being no /accumulo directory. While I understand we don't
want to worry about clobbering the directory, we should provide a mechanism to init on top
of an existing, but empty, /accumulo hdfs directory. This will allow the SA to create an accumulo
directory and provide perms appropriately for the accumulo user, rather than having to grant
write at the root level and then revoking that permission after initting.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message