[
https://issues.apache.org/jira/browse/ACCUMULO-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344060#comment-14344060
]
Christopher Tubbs commented on ACCUMULO-3631:
---------------------------------------------
What I mean is that the the classpath elements in the accumulo-site.xml file
are intended to configure server components, because that file is intended to
be a configuration file for server components, and its contents do not
*necessarily* reflect the runtime classpath needed for a client (or, more
broadly, everything possible to be run with accumulo-start).
You're right, we don't have such a thing as "client classpath". Regarding this,
one thing that [~kturner] and I have recently been discussing (because it'd be
convenient for Fluo) is this problem of how a service can provide information
to the client about a runtime "client classpath". Typically, it's some subset
of that service's own classpath, but it's not necessarily a subset, and even if
it were, figuring out which subset is difficult to do. Currently, a
"client-classpath" command in Accumulo would probably just return the location
of "accumulo-core.jar" and its dependencies (and transitive dependencies). In
the future, it might just return that of "accumulo-client.jar". But even then,
these may not even be on a filesystem which the client knows how to load from
(e.g.: vfs), because the client may not have a classloader to handle them.
> Exclude 'slf4j' artifacts from classpath in default value for
> general.classpaths
> --------------------------------------------------------------------------------
>
> Key: ACCUMULO-3631
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3631
> Project: Accumulo
> Issue Type: Bug
> Affects Versions: 1.6.0, 1.6.1, 1.6.2
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Blocker
> Fix For: 1.7.0, 1.6.3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Was testing out some Ambari integration for Accumulo that [~billie.rinaldi]
> and [~mwaineo] have been working on (AMBARI-5265) and found that, despite
> accumulo-site.xml having jars starting with slf4j excluded from the
> classpath, the shell would complain about duplicate slf4j-log4j12 jars on the
> classpath.
> Turns out, because access to accumulo-site.xml was restricted (and we only
> had client.conf to use), we fell back on the default value for
> general.classpaths defined in AccumuloClassLoader. A short-term fix is to
> update the value there to match what's in our site template.
> I'll add another issue for a long term fix to add classpath support to client
> configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
