You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "Jared Winick (Commented) (JIRA)" <ji...@apache.org> on 2012/01/01 04:46:30 UTC

[jira] [Commented] (ACCUMULO-240) client code for TableConfiguration has problems

    [ https://issues.apache.org/jira/browse/ACCUMULO-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178113#comment-13178113 ] 

Jared Winick commented on ACCUMULO-240:
---------------------------------------

I believe this bug describes the same issue as ACCUMULO-225, but in a more general way. If you agree, feel free to close ACCUMULO-225.
                
> client code for TableConfiguration has problems
> -----------------------------------------------
>
>                 Key: ACCUMULO-240
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-240
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.3.5
>            Reporter: Adam Fuchs
>            Assignee: Adam Fuchs
>
> 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 fail:
> {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(HdfsZooInstance.java:136)
> 	at org.apache.accumulo.core.client.impl.HdfsZooInstance.getInstanceID(HdfsZooInstance.java:123)
> 	at org.apache.accumulo.core.conf.ZooConfiguration.getInstanceId(ZooConfiguration.java:65)
> 	at org.apache.accumulo.core.conf.ZooConfiguration.iterator(ZooConfiguration.java:132)
> 	at org.apache.accumulo.core.conf.TableConfiguration.iterator(TableConfiguration.java:129)
> 	at org.apache.accumulo.core.conf.ConfigSanityCheck.validate(ConfigSanityCheck.java:29)
> 	at org.apache.accumulo.core.conf.AccumuloConfiguration.getTableConfiguration(AccumuloConfiguration.java:150)
> 	at org.apache.accumulo.core.client.admin.TableOperationsImpl.getProperties(TableOperationsImpl.java:544)
> 	at org.apache.accumulo.core.client.admin.TableOperationsImpl.setLocalityGroups(TableOperationsImpl.java:583)
> {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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira