You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pierre Villard (Jira)" <ji...@apache.org> on 2026/09/03 10:36:00 UTC
[jira] [Created] (NIFI-16286) Prevent stale Parameter Context provenance from breaking context retrieval
Pierre Villard created NIFI-16286:
-------------------------------------
Summary: 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
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)