[
https://issues.apache.org/jira/browse/ACCUMULO-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327618#comment-15327618
]
Dave Marion commented on ACCUMULO-3923:
---------------------------------------
I have some changes locally to bootstrap_hdfs.sh so that it will support the
following property values in general.vfs.classpaths:
hdfs://host:port/accumulo/classpath/
hdfs://host:port/accumulo/classpath/.*.jar
hdfs://host:port/accumulo/classpath/.*.jar,hdfs://host:port/accumulo/classpath2/.*.jar
In all cases, it will create the /accumulo/classpath if it does not exist and
push the jars from the lib directory into the specified directory. I also found
in my testing that the slf4j jars need to be kept on the local server.
Additionally, when trying to run `accumulo help` to test these changes, I found
that the client is in a deadlock situation. Ticket to follow.
> 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)
