[ https://issues.apache.org/jira/browse/MINIFI-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15586584#comment-15586584 ]
ASF GitHub Bot commented on MINIFI-117: --------------------------------------- GitHub user brosander opened a pull request: https://github.com/apache/nifi-minifi/pull/45 MINIFI-117 - Maintainable Configuration Versioning You can merge this pull request into a Git repository by running: $ git pull https://github.com/brosander/nifi-minifi MINIFI-117-3 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-minifi/pull/45.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #45 ---- commit 1f8f6e605dce1ab5dfab10f7a267e46c7c727bfe Author: Bryan Rosander <bryanrosan...@gmail.com> Date: 2016-10-07T17:23:21Z MINIFI-117 - Maintainable Configuration Versioning ---- > 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. > It should also facilitate a deprecation strategy of removing older versions' > classes without needing to touch current implementation -- This message was sent by Atlassian JIRA (v6.3.4#6332)