[
https://issues.apache.org/jira/browse/NIFI-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-16264:
------------------------------------
Summary: Resource Types and Scopes in Runtime Manifest lack deterministic
ordering (was: Resource Types in Runtime Manifest lack deterministic ordering)
> 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
>
> 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)
