accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-1694) ZooKeeperInstance constructor should avoid throwing RuntimeExceptions
Date Fri, 29 Nov 2013 18:25:38 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

John Vines resolved ACCUMULO-1694.
----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 1.7.0)
                   1.6.0

Resolved with ACCUMULO-1009 patch, I think

> ZooKeeperInstance constructor should avoid throwing RuntimeExceptions
> ---------------------------------------------------------------------
>
>                 Key: ACCUMULO-1694
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1694
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>            Reporter: 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
(v6.1#6144)

Mime
View raw message