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

Josh Elser commented on ACCUMULO-3631:
--------------------------------------

bq. this issue has shown that one can hit the default value in cases where one 
has taken care to change the defaults in the configuration files

That is a rather obvious case that I (shamefully) didn't consider.

bq. I'm reluctant to phrase my concerns as "blocker"

Sorry, didn't mean to put words in your mouth. Just meant to encapsulate your 
concerns.

I'll modify the default value in 1.6 to remove the addt'l entries and leave 1.7 
be. Where exactly do you think aforementioned documentation should exist [in 
the user manual] (?). 
http://accumulo.apache.org/1.6/accumulo_user_manual.html#_accumulo_settings ?

> 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)

Reply via email to