accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3631) Exclude 'slf4j' artifacts from classpath in default value for general.classpaths
Date Sat, 28 Feb 2015 02:17:04 GMT

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

Christopher Tubbs commented on ACCUMULO-3631:
---------------------------------------------

bq. I'd bring up that the system is currently broken and unusable given our recommended "production"
deployments.

Which recommendations are you referring to? Also, which brokenness are you referring to, specifically?
(I'm not clear on which part is unusable.) If that is the case, then it would certainly be
a point to consider.

bq. If this variable is not defined, it implies a lack of care in the administrator or client.
This is a point to consider with your security risks.

Agreed, but I was specifically thinking of the case raised here, where it is set, but inaccessible.

bq. You really don't need to be so brash. If you have concerns, like any other time, I'm happy
to work together and come up with a solution.

It is not my intention to be brash; it is to be direct and precise. I apologize if it came
across that way. Discussing to come to a solution is precisely what I'm intending to do here.
I was simply explaining my inclination, to convey my state of mind at that moment (pending
discussion).

I also agree that there's no urgency to revert, but it is an issue we need to resolve before
another release. We should make this a blocker to ensure that happens (in case this discussion
wanes before resolution).

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

Mime
View raw message