[
https://issues.apache.org/jira/browse/NIFI-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-3049:
------------------------------
Description:
The ZooKeeper Migrator Toolkit has a dependency on ZooKeeper 3.4.6 which has a
hard dependecy on log4j, which conflicts with nifi-property-loader's dependency
on logback. When the toolkit runs, SLF4J finds two logging implementations to
bind to and complains, and according to SLF4J's documentation, it is considered
random which implementation SLF4J will use.
The command line output should be modified to adhere to the standard
established by the other tools in the toolkit.
was:
The ZooKeeper Migrator Toolkit has a dependency on ZooKeeper 3.4.6 which has a
hard dependecy on log4j, which conflicts with nifi-property-loader's dependency
on logback. When the toolkit runs, SLF4J finds two logging implementations to
bind to and complains, and according to SLF4J's documentation, it is considered
random which implementation SLF4J will use.
The ZooKeeper Migrator Toolkit should also be modified to use ZooKeeper
client's chroot capablity using the connection string (with path appended to
it) rather than the migrator attempting to implement that with custom logic.
Finally, the command line output should be modified to adhere to the standard
established by the other tools in the toolkit.
> ZooKeeper Migrator Toolkit addition has broken logging in NiFI Toolkit and
> does not provide the correct command line usage output
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-3049
> URL: https://issues.apache.org/jira/browse/NIFI-3049
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
> Affects Versions: 1.1.0
> Reporter: Jeff Storck
> Assignee: Jeff Storck
>
> The ZooKeeper Migrator Toolkit has a dependency on ZooKeeper 3.4.6 which has
> a hard dependecy on log4j, which conflicts with nifi-property-loader's
> dependency on logback. When the toolkit runs, SLF4J finds two logging
> implementations to bind to and complains, and according to SLF4J's
> documentation, it is considered random which implementation SLF4J will use.
> The command line output should be modified to adhere to the standard
> established by the other tools in the toolkit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
