You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Martin Zink (Jira)" <ji...@apache.org> on 2024/08/02 10:05:00 UTC

[jira] [Updated] (MINIFICPP-2294) Add config migration step

     [ https://issues.apache.org/jira/browse/MINIFICPP-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Zink updated MINIFICPP-2294:
-----------------------------------
    Status: Patch Available  (was: In Progress)

> Add config migration step
> -------------------------
>
>                 Key: MINIFICPP-2294
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-2294
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: New Feature
>            Reporter: Martin Zink
>            Assignee: Martin Zink
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Often there is a comprimise fixing bugs and selecting the best approach due to the consideration of old config files.
> We could add a migration step (with config file versioning), and when we load an older config file we should do the neccessary update steps to fix the issues and save the config file with the new version. (Im not yet sure how it would work with C2 issued configs though)
> e.g.
> https://issues.apache.org/jira/browse/MINIFICPP-2042
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)