Skip to content

NIFI-6886: Fix issue with SiteToSite refreshing peers#3959

Closed
mattyb149 wants to merge 2 commits intoapache:masterfrom
mattyb149:NIFI-6886
Closed

NIFI-6886: Fix issue with SiteToSite refreshing peers#3959
mattyb149 wants to merge 2 commits intoapache:masterfrom
mattyb149:NIFI-6886

Conversation

@mattyb149
Copy link
Contributor

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?
  • Have you verified that the full build is successful on both JDK 8 and JDK 11?
  • 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.

eduardofontes and others added 2 commits January 6, 2020 16:40
Attribute peerPersistence can be null generating Bulletin WARNs "Unable to refresh Remote Group's peers due to null".

Rollback

The fix is inside site-to-site-reporting-task-bundle

Modify getClient()

Get ConfigurationContext and ReportingContext to provide a StateManager.

Modify OnScheduled setup()

The OnSchedule setup() now save the ConfigurationContext to lazily create a SiteToSiteClient with ReportingContext through an overloaded setup().

Modify OnTrigger

Lazily creates SiteToSiteClient to provide a StateManager

Modify OnTrigger

Lazily create SiteToSiteClient to provide a StateManager

Modify OnTrigger

Lazily create SiteToSiteClient to provide a StateManager

Modify OnTrigger

Lazily create SiteToSiteClient to provide a StateManager

Retry compile

Fix maven-checkstyle-plugin

Fix maven-checkstyle-plugin

Fix maven-checkstyle-plugin

Fix maven-checkstyle-plugin

Update AbstractSiteToSiteReportingTask.java

Removed the OnSchedule setup(ConfigContext) because it is not needed.

Update SiteToSiteUtils.java

Removed ConfigContext from getClient parameters because ReportContext share the same properties.
@shawnweeks
Copy link
Contributor

My test runs fine on the new build. +1

@asfgit asfgit closed this in 9ed4623 Jan 7, 2020
@pvillard31
Copy link
Contributor

Merged to master, thanks @mattyb149 @shawnweeks @eduardofontes

patricker pushed a commit to patricker/nifi that referenced this pull request Jan 22, 2020
Signed-off-by: Pierre Villard <pierre.villard.fr@gmail.com>

This closes apache#3959.
natural pushed a commit to natural/nifi that referenced this pull request Feb 1, 2020
Signed-off-by: Pierre Villard <pierre.villard.fr@gmail.com>

This closes apache#3959.
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.

4 participants