You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Bryan Rosander (JIRA)" <ji...@apache.org> on 2016/10/05 18:32:20 UTC
[jira] [Assigned] (MINIFI-117) Maintainable Configuration
Versioning
[ https://issues.apache.org/jira/browse/MINIFI-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Rosander reassigned MINIFI-117:
-------------------------------------
Assignee: Bryan Rosander
> Maintainable Configuration Versioning
> -------------------------------------
>
> Key: MINIFI-117
> URL: https://issues.apache.org/jira/browse/MINIFI-117
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Reporter: Bryan Rosander
> Assignee: Bryan Rosander
>
> In order to avoid a tangled web of if/else statements around every possible permutation of config.yml and an equally complicated validation routine, we need to utilize a versioning strategy that allows for specific parsing and validation code for each version of the ConfigSchema.
> This will allow us to determine if a schema will be compatible with an older MiNiFi instance more easily by validating the structure of the file at a given version while still supporting an upconvert on read to the latest ConfigSchema while parsing at runtime.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)