[ https://issues.apache.org/jira/browse/ACCUMULO-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326496#comment-15326496 ]
Dave Marion commented on ACCUMULO-3923: --------------------------------------- bq. It is not clear at all what general.vfs.classpaths value is supposed to be. A directory? A java classpath style wildcard? A regex for jars? >From the example in the >[blog|https://blogs.apache.org/accumulo/entry/the_accumulo_classloader] {noformat} <property> <name>general.vfs.classpaths</name> <value>hdfs://localhost:8020/accumulo/system-classpath</value> <description>Configuration for a system level vfs classloader. Accumulo jars can be configured here and loaded out of HDFS.</description> </property> {noformat} You should be able to do the following: 1. Untar an accumulo distribution somewhere 2. create the configuration files (bootstrap_config.sh) 3. Make appropriate changes to accumulo-env.sh and accumulo-site.xml, to include the property above 4. Run bootstrap_hdfs.sh, this will push most of the jars into the location specified in the general.vfs.classpaths property 5. Do what Christopher suggested [above|https://issues.apache.org/jira/browse/ACCUMULO-3923?focusedCommentId=15308710&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15308710] > VFS ClassLoader doesnt' work with KeywordExecutable > --------------------------------------------------- > > Key: ACCUMULO-3923 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3923 > Project: Accumulo > Issue Type: Bug > Reporter: Josh Elser > Assignee: Dave Marion > Priority: Critical > Fix For: 1.7.3, 1.8.0 > > > Trying to make the VFS classloading stuff work and it doesn't seem like > ServiceLoader is finding any of the KeywordExecutable implementations. > Best I can tell after looking into this, VFSClassLoader (created by > AccumuloVFSClassLoader) has all of the jars listed as resources, but when > ServiceLoader tries to find the META-INF/services definitions, it returns > nothing, and thus we think the keyword must be a class name. Seems like a > commons-vfs bug. -- This message was sent by Atlassian JIRA (v6.3.4#6332)