accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <>
Subject [jira] [Assigned] (ACCUMULO-1694) ZooKeeperInstance constructor should avoid throwing RuntimeExceptions
Date Sat, 26 Oct 2013 02:41:31 GMT


John Vines reassigned ACCUMULO-1694:

    Assignee: John Vines

> ZooKeeperInstance constructor should avoid throwing RuntimeExceptions
> ---------------------------------------------------------------------
>                 Key: ACCUMULO-1694
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>            Reporter: John Vines
>            Assignee: John Vines
>             Fix For: 1.6.0
> Currently all ZooKeeper related exceptions that occur in ZooKeeperInstance's constructor
get propagated out as RuntimeExceptions. We should change this behavior to allow for better
client handling of configuration issues.
> I think the best options are to either have the constructor throw an exception for this
(which I'm a bit meh on) or having methods which actually need to talk to ZooKeeper propagate
a non-runtime exception. We can easily wrap this under AccumuloException for getConnector,
I think, but getMasterLocations() and getRootTabletLocation() would also have to propagate
an error which would mean an interface change.

This message was sent by Atlassian JIRA

View raw message