[
https://issues.apache.org/jira/browse/NIFI-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17410765#comment-17410765
]
David Handermann commented on NIFI-9183:
----------------------------------------
Thanks for the reply [~Lehel44]. From the initial description, it sounded like
the script might be calling a REST API, but now seeing the PR, I realize that
was the not the implementation approach. With that background, I think the
approach you implemented in the PR, with a separate command under {{nifi.sh}}
seems reasonable.
> Add a command-line option to save status history
> ------------------------------------------------
>
> Key: NIFI-9183
> URL: https://issues.apache.org/jira/browse/NIFI-9183
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Lehel Boér
> Assignee: Lehel Boér
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The status history can only be accessed via the nifi-api REST endpoint. Given
> that these API calls are replicated across cluster nodes, we should add a
> command-line option to save the status history of only one node.
> {{./bin/nifi.sh status-history <days> <dumpFile>}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
