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] [Resolved] (ACCUMULO-3496) ZooKeeperInstance doesn't validate instance name on creation
Date Mon, 19 Jan 2015 21:17:34 GMT

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

Josh Elser resolved ACCUMULO-3496.
----------------------------------
    Resolution: Fixed

> ZooKeeperInstance doesn't validate instance name on creation
> ------------------------------------------------------------
>
>                 Key: ACCUMULO-3496
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3496
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.6.0, 1.6.1
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Blocker
>             Fix For: 1.6.2, 1.7.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> ZooKeeperInstance in 1.5 contained a check when the instance name was used to ensure
that a real instanceName was provided.
> {code}
>  public ZooKeeperInstance(String instanceName, String zooKeepers, int sessionTimeout)
{
>      ArgumentChecker.notNull(instanceName, zooKeepers);
>      this.instanceName = instanceName;
>      this.zooKeepers = zooKeepers;
>      this.zooKeepersSessionTimeOut = sessionTimeout;
>      zooCache = ZooCache.getInstance(zooKeepers, sessionTimeout);
>      getInstanceID();
>    }
> {code}
> The call to {{getInstanceID()}} throws an exception if the instanceName didn't exist
in ZK.
> In 1.6, this check no longer exists and will only happen when the ZKI is actually used
(typically on getConnector(...)).
> Restore the check when the instance name is provided.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message