accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2076) Make it easier to connect to acccumulo
Date Thu, 26 Dec 2013 19:13:50 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13857005#comment-13857005
] 

Josh Elser commented on ACCUMULO-2076:
--------------------------------------

bq. In theory, I'm fine with any fix version <= 1.7; in practice, I'm writing utilities
and applications against 1.4 and 1.5 and I absolutely intend to use this in my own code, even
if I have to refactor into an external utility class.

I think [~kturner] is rubbing off on me a little bit because the first thing I thought about
was the potential confusion over adding something like this to the 5th bugfix release to a
version of Accumulo that's already about a year old (1.4.5). Ultimately, the current mechanism
isn't *that* pedantic to use that it necessitates us pulling back these changes everywhere
IMO. As it stands, I really would only want to see this in 1.7.0 (or whatever is "next" after
1.6.0).

In fact, I think it would be pretty swanky to be able to do something like {{Instances.newZooKeeperInstance}}
or {{Instances.newMockInstance}} and even get into more fluent like {{Instances.newZooKeeperInstance().withClasspath()}}
or something. Making the API easier to use likely isn't something we'll get right the first
go. I'd rather sit on it for a little bit and make sure we're all happy with it before tossing
it into a release and having deprecation churn.

> 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)

Mime
View raw message