You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "John Vines (JIRA)" <ji...@apache.org> on 2013/09/06 19:49:53 UTC

[jira] [Created] (ACCUMULO-1694) ZooKeeperInstance constructor should avoid throwing RuntimeExceptions

John Vines created ACCUMULO-1694:
------------------------------------

             Summary: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira