Skip to content

NIFI-6028: Updates to ignore changes between local version of a flow …#3544

Closed
markap14 wants to merge 2 commits intoapache:masterfrom
markap14:NIFI-6028
Closed

NIFI-6028: Updates to ignore changes between local version of a flow …#3544
markap14 wants to merge 2 commits intoapache:masterfrom
markap14:NIFI-6028

Conversation

@markap14
Copy link
Contributor

…and a remote version of a flow if the difference is the addition of a new property that has the default value

Thank you for submitting a contribution to Apache NiFi.

Please provide a short description of the PR here:

Description of PR

Enables X functionality; fixes bug NIFI-YYYY.

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 master)?

  • 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 squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

  • Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
  • Have you written or updated unit tests to verify your changes?
  • If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
  • If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
  • If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
  • If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

  • Have you ensured that format looks appropriate for the output in which it is rendered?

Note:

Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

…and a remote version of a flow if the difference is the addition of a new property that has the default value
@mcgilman
Copy link
Contributor

Will review...

return false;
}

private static boolean isNewPropertyWithDefaultValue(final FlowDifference fd, final ProcessorNode processorNode) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This method appears to be overloaded below. However, the parameter that differs shares a common ancestor interface. I think we can update the args to use a ComponentNode and remove the duplicated code.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

D'oh, good point! Will push a new commit that takes advantage of this.

@mcgilman
Copy link
Contributor

Outside of the minor comment above, I am a +1 for this PR. However, we cannot merge it in as it requires a new version of NiFi Registry. Once the Registry is released, we should be good to merge this in.

@bbende
Copy link
Contributor

bbende commented Aug 28, 2019

I tested this with nifi.registry.version set to the released 0.5.0 version and all looks good, going to merge

@asfgit asfgit closed this in 59734da Aug 28, 2019
szaboferee pushed a commit to szaboferee/nifi that referenced this pull request Oct 7, 2019
…and a remote version of a flow if the difference is the addition of a new property that has the default value

NIFI-6028: Code refactoring to address review feedback

This closes apache#3544.

Signed-off-by: Bryan Bende <bbende@apache.org>
patricker pushed a commit to patricker/nifi that referenced this pull request Jan 22, 2020
…and a remote version of a flow if the difference is the addition of a new property that has the default value

NIFI-6028: Code refactoring to address review feedback

This closes apache#3544.

Signed-off-by: Bryan Bende <bbende@apache.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants