[
https://issues.apache.org/jira/browse/NIFI-14877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Bean updated NIFI-14877:
-----------------------------
Description:
It is desirable to be able to bulk update connection settings. Specifically,
the settings for FlowFile Expiration, Back Pressure Object Threshold and Size
Threshold. These settings may have been set initially by inheriting the default
values specified at the process group level. After initial build-out of a flow,
it may be determined the default settings need to be updated. This requires
going to dozens or perhaps hundreds of connections individually to update.
A new option to bulk update all connections would make the process easier, less
time-consuming and less error-prone. This feature would be similar in
convenience to the bulk operation of "Empty All Queues".
Since it is being applied in bulk, a warning/confirmation pop-up should be
displayed - again, similar to the "Empty All Queues" option.
>From a UI/UX perspective, a new item on the context menu can be added. The
>FlowFile Expiration and Back Pressure settings should be treated separately.
>So, there can be a main context menu item "Update Connections" with two
>sub-menu choices, "Apply Default Expiration" and "Apply Default Back
>Pressure".
For each option, the respective default FlowFile expiration or default back
pressure settings (both object and size) of the containing Process Group would
be applied to all Connections within the Process Group.
After a selection is made, a pop-up can be displayed asking "Apply
recursively?" (Appropriately detailed wording should be provided.) Confirmation
buttons for "Yes", "No" and "Cancel" should be available.
Careful consideration needs to be applied to this issue. Specifically,
Connection settings can only be updated if the upstream and downstream
processors are in a non-running state. If automatically stopping a processor,
it must be restarted again (but only if it was stopped in this process and not
in a stopped state initially.) Other considerations include a cluster
environment: what if one node takes an excessively long time to stop a
processor while other nodes complete the Connection setting update?
was:
It is desirable to be able to bulk update connection settings. Specifically,
the settings for FlowFile Expiration, Back Pressure Object Threshold and Size
Threshold. These settings may have been set initially by inheriting the default
values specified at the process group level. After initial build-out of a flow,
it may be determined the default settings need to be updated. This requires
going to dozens or perhaps hundreds of connections individually to update.
A new option to bulk update all connections would make the process easier, less
time-consuming and less error-prone. This feature would be similar in
convenience to the bulk operation of "Empty All Queues".
Since it is being applied in bulk, a warning/confirmation pop-up should be
displayed - again, similar to the "Empty All Queues" option.
>From a UI/UX perspective, a new item on the context menu can be added. The
>FlowFile Expiration and Back Pressure settings should be treated separately.
>So, there can be a main context menu item "Update Connections" with two
>sub-menu choices, "Apply Default Expiration" and "Apply Default Back
>Pressure".
For each option, the respective default FlowFile expiration or default back
pressure settings (both object and size) of the containing Process Group would
be applied to all Connections within the Process Group.
After a selection is made, a pop-up can be displayed asking "Apply
recursively?" (Appropriately detailed wording should be provided.) Confirmation
buttons for "Yes", "No" and "Cancel" should be available.
> Allow bulk update of connection settings
> ----------------------------------------
>
> Key: NIFI-14877
> URL: https://issues.apache.org/jira/browse/NIFI-14877
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Mark Bean
> Priority: Major
>
> It is desirable to be able to bulk update connection settings. Specifically,
> the settings for FlowFile Expiration, Back Pressure Object Threshold and Size
> Threshold. These settings may have been set initially by inheriting the
> default values specified at the process group level. After initial build-out
> of a flow, it may be determined the default settings need to be updated. This
> requires going to dozens or perhaps hundreds of connections individually to
> update.
> A new option to bulk update all connections would make the process easier,
> less time-consuming and less error-prone. This feature would be similar in
> convenience to the bulk operation of "Empty All Queues".
> Since it is being applied in bulk, a warning/confirmation pop-up should be
> displayed - again, similar to the "Empty All Queues" option.
> From a UI/UX perspective, a new item on the context menu can be added. The
> FlowFile Expiration and Back Pressure settings should be treated separately.
> So, there can be a main context menu item "Update Connections" with two
> sub-menu choices, "Apply Default Expiration" and "Apply Default Back
> Pressure".
> For each option, the respective default FlowFile expiration or default back
> pressure settings (both object and size) of the containing Process Group
> would be applied to all Connections within the Process Group.
> After a selection is made, a pop-up can be displayed asking "Apply
> recursively?" (Appropriately detailed wording should be provided.)
> Confirmation buttons for "Yes", "No" and "Cancel" should be available.
> Careful consideration needs to be applied to this issue. Specifically,
> Connection settings can only be updated if the upstream and downstream
> processors are in a non-running state. If automatically stopping a processor,
> it must be restarted again (but only if it was stopped in this process and
> not in a stopped state initially.) Other considerations include a cluster
> environment: what if one node takes an excessively long time to stop a
> processor while other nodes complete the Connection setting update?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
