You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by GitBox <gi...@apache.org> on 2022/10/21 21:53:28 UTC

[GitHub] [nifi] genehynson commented on pull request #6560: NIFI-10676 USE_SPECIFIED_OR_COMPATIBLE_OR_GHOST on flow load from bytes

genehynson commented on PR #6560:
URL: https://github.com/apache/nifi/pull/6560#issuecomment-1287472069

   Thanks for providing this insight @markap14 . Originally I thought this was a bug because of the inconsistency of loading the flow definition from a file vs from the connection response - but I understand now that its intentional. 
   
   I've been using this change on a fork of NiFi for 6 months or so now and haven't run into any of the edge cases you've identified but I understand that they can exist. And I certainly don't want to introduce a change that adds unwanted risk to the normal NiFi upgrade process. 
   
   Would you be open to the idea of introducing this change as an opt-in feature that is enabled with a flag in `nifi.properties`? That would allow more folks to test this capability in a "use at your own risk" fashion so we could better understand the impact and what additional changes would be necessary to fully support rolling upgrades in the future.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@nifi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org