[
https://issues.apache.org/jira/browse/ACCUMULO-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13857000#comment-13857000
]
Josh Elser edited comment on ACCUMULO-2076 at 12/26/13 7:06 PM:
----------------------------------------------------------------
(Discussion taken from review board.)
{quote}
[~elserj] wrote:
Wait, I just noticed that you have this RB marked as 1.4.5-SNAPSHOT (and your
javadoc has @since 1.4.5, etc) but your original ticket is marked for 1.7.0. I
do not think this should pushed back to 1.4.5 or 1.5.1. What is your intent?
Also, I was just talking to [~bills] about creating Instances earlier by
chance. Have you considered expanding this to also support HdfsZooInstance and
MiniAccumuloInstance? This would also give us flexibility in (if we move this
direction) to having threadsafe and non-threadsafe variants of the
aforementioned Instances (also moving towards a fluent interface like
[~bhavanki] mentioned).
{quote}
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.
Expanding this to HZI and MAI (and MockInstance?) is a good idea. I hadn't
implemented those because I consider them relatively trivial after there is
something for ZKI, and was more concerned about getting the first one right.
was (Author: mdrob):
(Discussion taken from review board.)
{quote}
[~elserj] wrote:
Wait, I just noticed that you have this RB marked as 1.4.5-SNAPSHOT (and your
javadoc has @since 1.4.5, etc) but your original ticket is marked for 1.7.0. I
do not think this should pushed back to 1.4.5 or 1.5.1. What is your intent?
Also, I was just talking to Bill Slacum about creating Instances earlier by
chance. Have you considered expanding this to also support HdfsZooInstance and
MiniAccumuloInstance? This would also give us flexibility in (if we move this
direction) to having threadsafe and non-threadsafe variants of the
aforementioned Instances (also moving towards a fluent interface like Bill
Havanki mentioned).
{quote}
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.
Expanding this to HZI and MAI (and MockInstance?) is a good idea. I hadn't
implemented those because I consider them relatively trivial after there is
something for ZKI, and was more concerned about getting the first one right.
> 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)
