[
https://issues.apache.org/jira/browse/NIFI-16286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18112359#comment-18112359
]
ASF subversion and git services commented on NIFI-16286:
--------------------------------------------------------
Commit 14fa8a2fb03e7a11320119054bb8cc05a8202b8f in nifi's branch
refs/heads/main from Pierre Villard
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=14fa8a2fb03 ]
NIFI-16286 Prevent stale Parameter Context provenance from breaking Context
retrieval (#11618)
Signed-off-by: David Handermann <[email protected]>
> Prevent stale Parameter Context provenance from breaking context retrieval
> --------------------------------------------------------------------------
>
> Key: NIFI-16286
> URL: https://issues.apache.org/jira/browse/NIFI-16286
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Parameter Context update requests can round-trip effective Parameter DTOs
> containing source-context metadata and incorrectly persist that
> client-supplied context ID on a locally accepted Parameter. If the referenced
> source context is later deleted, the stale provenance can cause Parameter
> Context listing, detail retrieval, or effective-update analysis to fail withÂ
> ResourceNotFoundException. Normalize locally accepted Parameters so ownership
> is determined by the target context, preserve valid inherited provenance, and
> make DTO rendering and update analysis tolerate missing or concurrently
> removed source contexts with value-safe warning diagnostics. Add unit,
> standalone, and clustered regression coverage for local, provided,
> asset-backed, inherited, missing-source, and concurrent-removal scenarios.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
