[
https://issues.apache.org/jira/browse/ACCUMULO-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997887#comment-13997887
]
Josh Elser commented on ACCUMULO-2076:
--------------------------------------
ACCUMULO-2806 mentions securing the directories in HDFS via FileSystem
permissions in which Accumulo will write any data which is sensitive as a
work-around to securing the entire Accumulo parent directory. This is necessary
because client-facing tools (shell, most notably) require access to the
{{instance_id}} in HDFS, and would likely be denied access.
The solution implemented here should allow for transparent use of tools with an
existing Accumulo instance without access to files/dirs within Accumulo's HDFS
structure.
> Make it easier to connect to acccumulo
> --------------------------------------
>
> Key: ACCUMULO-2076
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2076
> Project: Accumulo
> Issue Type: Sub-task
> Components: client
> Reporter: Mike Drob
> Priority: Minor
> Fix For: 1.7.0
>
>
> Given a program that has {{accumulo-site.xml}} on its classpath, we should be
> able to abstract away from the user the steps for connecting to accumulo. I'm
> thinking that we need to expose something like HdfsZooInstance through the
> client API, but not exactly that, since HZI looks like it carries some extra
> functionality.
> # Determine the backing file system
> # Get Instance ID from the FS.
> # Get ZooServers from accumulo-site.xml
> # Get Instance Name from ZK.
> # Create an Instance and hand it to the user.
> If this already exists in master, then maybe we need to do a better job of
> documenting. Or a better job of educating me.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
