NIFI-9229 Flow upgrade not possible if a Output Port changes to a funnel#5402
Merged
adenes merged 2 commits intoapache:mainfrom Oct 4, 2021
Merged
NIFI-9229 Flow upgrade not possible if a Output Port changes to a funnel#5402adenes merged 2 commits intoapache:mainfrom
adenes merged 2 commits intoapache:mainfrom
Conversation
e9de70b to
76d8b31
Compare
76d8b31 to
2bb400a
Compare
adenes
suggested changes
Oct 1, 2021
Contributor
adenes
left a comment
There was a problem hiding this comment.
Thanks @timeabarna for the fix. Overall the change looks good to me and works as expected. I only had a few minor comments.
...ork/nifi-framework-components/src/main/java/org/apache/nifi/groups/StandardProcessGroup.java
Outdated
Show resolved
Hide resolved
...ork/nifi-framework-components/src/main/java/org/apache/nifi/groups/StandardProcessGroup.java
Outdated
Show resolved
Hide resolved
...ork/nifi-framework-components/src/main/java/org/apache/nifi/groups/StandardProcessGroup.java
Show resolved
Hide resolved
...ork/nifi-framework-components/src/main/java/org/apache/nifi/groups/StandardProcessGroup.java
Outdated
Show resolved
Hide resolved
Contributor
Author
|
Thanks @adenes for your help, I've modified the code based on your recommendations. |
adenes
approved these changes
Oct 4, 2021
Contributor
adenes
left a comment
There was a problem hiding this comment.
Thanks @timeabarna for the follow-up commit, the fix looks good to me. Merging to main.
krisztina-zsihovszki
pushed a commit
to krisztina-zsihovszki/nifi
that referenced
this pull request
Jun 28, 2022
…nel (apache#5402) * NIFI-9229 Flow upgrade not possible if a Output Port changes to a funnel * NIFI-9229 Addressing review comments modified log message and added comments
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://issues.apache.org/jira/browse/NIFI-9229
Description of PR
Fixing bug NIFI-9229
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
Has your PR been rebased against the latest commit within the target branch (typically
main)?Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not
squashor use--forcewhen pushing to allow for clean monitoring of changes.For code changes:
mvn -Pcontrib-check clean installat the rootnififolder?LICENSEfile, including the mainLICENSEfile undernifi-assembly?NOTICEfile, including the mainNOTICEfile found undernifi-assembly?.displayNamein addition to .name (programmatic access) for each of the new properties?For documentation related changes:
Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.