[
https://issues.apache.org/jira/browse/ACCUMULO-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14341190#comment-14341190
]
Josh Elser commented on ACCUMULO-3631:
--------------------------------------
bq. as they are hard-coded directly into the default behavior of Accumulo,
which matters in production (for reasons outlined in this issue, and probably
other reasons, also).
I'd bring up that the system is currently broken and *unusable* given our
recommended "production" deployments. As ACCUMULO-3632 can't be done in 1.6, I
think you need to temper your concerns with the current state of things.
bq. I'm also opposed to these additional items on the default classpath for
1.6, due to the fact that it intrinsically changes the security risks and
considerations admins have made for that version, across a bugfix release, and
I think such a change is inappropriate in a bugfix release.
That is a valid concern. I weight it against the inability to function in the
case where the value is not defined. *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.
bq. I'm inclined to -1 this change and revert the commit
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. We have no
releases planned, so there's no reason this must be immediately resolved. We
can work through it without being antisocial.
> 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)
