accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Resolved] (ACCUMULO-240) client code for TableConfiguration has problems
Date Tue, 18 Dec 2012 19:30:12 GMT


Christopher Tubbs resolved ACCUMULO-240.

       Resolution: Fixed
    Fix Version/s:     (was: 1.5.0)
> client code for TableConfiguration has problems
> -----------------------------------------------
>                 Key: ACCUMULO-240
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.3.5
>            Reporter: Adam Fuchs
>            Assignee: Adam Fuchs
>             Fix For: 1.4.2
> There are a number of problems with accessing TableConfiguration object from client code,
the first being that TableOperationImpl uses code that relies on a hidden HDFSZooInstance
in client configuration. If the client is not running with access to the HDFS Accumulo directory,
or if the HDFS setup on the client differs from the Accumulo instance, then this call will
> {noformat}
> Exception in thread "main" java.lang.ExceptionInInitializerError
> Caused by: org.apache.accumulo.core.client.impl.HdfsZooInstance$AccumuloNotInitializedException:
Accumulo not initialized, there is no instance id at /accumulo/instance_id
> 	at org.apache.accumulo.core.client.impl.HdfsZooInstance._getInstanceID(
> 	at org.apache.accumulo.core.client.impl.HdfsZooInstance.getInstanceID(
> 	at org.apache.accumulo.core.conf.ZooConfiguration.getInstanceId(
> 	at org.apache.accumulo.core.conf.ZooConfiguration.iterator(
> 	at org.apache.accumulo.core.conf.TableConfiguration.iterator(
> 	at org.apache.accumulo.core.conf.ConfigSanityCheck.validate(
> 	at org.apache.accumulo.core.conf.AccumuloConfiguration.getTableConfiguration(
> 	at org.apache.accumulo.core.client.admin.TableOperationsImpl.getProperties(
> 	at org.apache.accumulo.core.client.admin.TableOperationsImpl.setLocalityGroups(
> {noformat}
> Another problem is that the ZooConfiguration object uses static instance information,
negating the possibility of using multiple instances in the same JVM.

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:

View raw message