You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "John Vines (Resolved) (JIRA)" <ji...@apache.org> on 2012/01/05 20:08:39 UTC

[jira] [Resolved] (ACCUMULO-225) Setting Locality Groups via the API throws an exception

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

John Vines resolved ACCUMULO-225.
---------------------------------

    Resolution: Duplicate

Duplicate of Accumulo-240
                
> Setting Locality Groups via the API throws an exception
> -------------------------------------------------------
>
>                 Key: ACCUMULO-225
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-225
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client, docs
>    Affects Versions: 1.3.5
>            Reporter: Jared Winick
>            Assignee: Billie Rinaldi
>            Priority: Minor
>
> If a client attempts to set locality groups via the API and the client does not have core-site.xml on its classpath, the following exception is thrown after the groups are actually successfully set.
> Exception in thread "main" org.apache.accumulo.core.client.impl.HdfsZooInstance$AccumuloNotInitializedException: Accumulo not initialized, there is no instance id at /accumulo/instance_id
> The exception is confusing because:
> 1) the group(s) are actually created successfully
> 2) the exception misleads the user to believe there is something wrong with Accumulo's configuration where the problem is that the client isn't actually connecting to HDFS properly because it is missing core-site.xml on its classpath.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira