[
https://issues.apache.org/jira/browse/ACCUMULO-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856055#comment-13856055
]
Josh Elser commented on ACCUMULO-2076:
--------------------------------------
bq. The accumulo-site.xml file used by servers has a secret that client should
not see.
This has come up a couple of times recently about how the accumulo-site.xml
file isn't necessarily good to client consumption. Would it be better to think
about how we can split up the logic into client and server xml files and make
sure we get make decisions about how to structure said files from a
segmentation of configuration params (for server and for public use) and for
ease of API use.
> Make it easier to connect to acccumulo
> --------------------------------------
>
> Key: ACCUMULO-2076
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2076
> Project: Accumulo
> Issue Type: Improvement
> 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.1.5#6160)
