[
https://issues.apache.org/jira/browse/ACCUMULO-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240731#comment-13240731
]
John Vines commented on ACCUMULO-500:
-------------------------------------
Addendum- not just /accumulo, but whatever the directory is set to.
P.S. sorry for wasting ticket 500 on something so trite
> 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
>
> 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
