[
https://issues.apache.org/jira/browse/NIFI-15243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-15243:
------------------------------------
Fix Version/s: 2.8.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Improve logic for set and replace state in KubernetesConfigMapStateProvider
> ---------------------------------------------------------------------------
>
> Key: NIFI-15243
> URL: https://issues.apache.org/jira/browse/NIFI-15243
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 2.6.0
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Major
> Fix For: 2.8.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> There are two areas for improvement...
> # In setState it uses the `update` method in the fabric8 client which under
> the hood performs a get of the resource and extracts the resourceVersion,
> puts the resourceVersion into the resource that was submitted, and overwrites
> whatever was there. In the case anything else in the k8s cluster added
> additional metadata to the ConfigMap, this will remove it by replacing the
> resource without it.
> # In replace there is a similar situation where the retry logic for a 409
> retrieves the latest resource and extracts the resourceVersion and then uses
> that, but will call update and fully replace the resource.
> Both of these scenarios can be improved to honor the original intent of the
> API, but also preserve metadata on the resource.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
