[jira] [Commented] (NIFI-15838) GitHubFlowRegistryClient approach doesn't preserve prioritizer order

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-15838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18075239#comment-18075239 ] 

ASF subversion and git services commented on NIFI-15838:
--------------------------------------------------------

Commit 8b6797bcbe92c9fde535ca389fd6e9a9cf761a50 in nifi's branch refs/heads/main from Pierre Villard
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=8b6797bcbe9 ]

NIFI-15838 Preserve prioritizer order in Git flow Registry serialization (#11140)

Signed-off-by: David Handermann <ex...@apache.org>

> 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
>          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)