[
https://issues.apache.org/jira/browse/NIFI-15838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-15838:
------------------------------------
Fix Version/s: 2.10.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> GitHubFlowRegistryClient approach doesn't preserve prioritizer order
> --------------------------------------------------------------------
>
> Key: NIFI-15838
> URL: https://issues.apache.org/jira/browse/NIFI-15838
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Alexis Sarda-Espinosa
> Assignee: Pierre Villard
> Priority: Major
> Fix For: 2.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Based on our experiments it seems like the JSON array with the prioritizers
> is sorted before committing, so if a user configures multiple prioritizers
> for a queue, orders them in a way that doesn't end up being alphabetical, and
> commits them, they may later get a local change shown in the UI because the
> order differs. Committing again doesn't help in that case.
> Moreover, importing the processor group from git in a separate NiFi instance
> will then result in a different prioritizer order.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
