[
https://issues.apache.org/jira/browse/NIFI-15139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18034407#comment-18034407
]
ASF subversion and git services commented on NIFI-15139:
--------------------------------------------------------
Commit b586cd189da472cd607a72529b8314e69b5f9206 in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b586cd189d ]
NIFI-15139 Fixed bootstrap diagnostics argument handling
- Refactored diagnostics command handling to support verbose and output path
arguments together
Signed-off-by: Pierre Villard <[email protected]>
This closes #10469.
> Nifi diagnostic command is not save output to a file, if verbose option is
> also used
> ------------------------------------------------------------------------------------
>
> Key: NIFI-15139
> URL: https://issues.apache.org/jira/browse/NIFI-15139
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Zoltán Kornél Török
> Assignee: Zoltán Kornél Török
> Priority: Minor
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> When I wanted to use nifi diagnostics output, it turned out that the
> functionality is broken. It seems if I define the --verbose argument and a
> file name then the command output will be put into the default
> nifi-bootstrap.log.
> For example:
> {code:java}
> nifi.sh diagnostics --verbose /tmp/test
> {code}
> or
> {code:java}
> nifi.sh diagnostics /tmp/test --verbose {code}
> Don't save to the file, if --verbose is used. As it turned out there is a
> part in the code which assumes that the arguments are always two -
> [https://github.com/apache/nifi/blob/main/nifi-bootstrap/src/main/java/org/apache/nifi/bootstrap/command/StandardBootstrapCommandProvider.java#L155]
>
> However that will not work, if I define --verbose as well. My fix first will
> be filter out --verbose, and after will check that is there a filename or not.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
