[
https://issues.apache.org/jira/browse/NIFI-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Witt updated NIFI-3067:
------------------------------
Fix Version/s: (was: 1.2.0)
> Upgrade ZooKeeper dependency version
> ------------------------------------
>
> Key: NIFI-3067
> URL: https://issues.apache.org/jira/browse/NIFI-3067
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework, Tools and Build
> Affects Versions: 1.0.0, 1.1.0
> Reporter: Jeff Storck
>
> ZooKeeper 3.4.6 has dependencies on log4j, although it uses slf4j as the
> logging API; if the log4j dependency is excluded from ZooKeeper 3.4.6 in
> favor of using logback, ZooKeeper has runtime issues.
> ZooKeeper 3.4.6's hard dependency on log4j has caused issues in NiFi Toolkit,
> which originally used logback. When the ZooKeeper Migrator was added to NiFi
> Toolkit, the log4j dependency came with it, which broke the logging in NiFi
> Toolkit due to having both logback and log4j on the classpath. To resolve
> the issue in NiFI Toolkit, the logback dependency has been removed, and it
> now explicitly uses log4j.
> In ZooKeeper 3.5.2 and 3.6.0, the dependency on log4j has been removed. NiFi
> (and the Toolkit) would benefit from upgrading to one of these versions of
> ZooKeeper, allowing the usage of log4j or logback without the classpath and
> runtime issues mentioned above.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
