[
https://issues.apache.org/jira/browse/NIFI-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18109810#comment-18109810
]
ASF subversion and git services commented on NIFI-16264:
--------------------------------------------------------
Commit 8f56dfb26860fa901ea1ad8b35fe0d97fe7cef5d in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=8f56dfb2686 ]
NIFI-16264 Set order for Resource Types and Scopes in Manifest (#11598)
> Resource Types and Scopes in Runtime Manifest lack deterministic ordering
> -------------------------------------------------------------------------
>
> Key: NIFI-16264
> URL: https://issues.apache.org/jira/browse/NIFI-16264
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Tools and Build
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The Standard Runtime Manifest Builder writes Property Descriptors with
> Resource Types using the simple Collectors.toSet() method, which results in
> non-deterministic order for the set enumerated Resource Types.
> The Resource Types for applicable Property Descriptors should use a
> LinkedHashSet to preserve deterministic order across multiple builds.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
