NIFI-4343 - allow multiple URLs in SiteToSite reporting tasks#2121
NIFI-4343 - allow multiple URLs in SiteToSite reporting tasks#2121pvillard31 wants to merge 3 commits intoapache:masterfrom
Conversation
|
@pvillard31 I looked at the change briefly. I think we also need to change to use |
|
Good catch @ijokarumawak and thanks for the review. Just pushed a commit to address your comment. |
|
|
||
| siteToSiteClient = new SiteToSiteClient.Builder() | ||
| .url(destinationUrl) | ||
| .urls(SiteToSiteRestApiClient.parseClusterUrls(destinationUrl)) |
There was a problem hiding this comment.
This change just reminded me that SiteToSiteRestApiClient.parseClusterUrls also validates the destinationUrl. Probably it'd be a better approach to use SiteToSiteRestApiClient.parseClusterUrls and catch IllegalArgumentException from NiFiUrlValidator.validate(), instead of implementing different validation code there. How do you think?
|
@pvillard31 Thanks for the update. I've confirmed that SiteToSiteProvenanceReportingTask can use comma separated URLs, and stay being able to send events even if one of the remote NiFi instances specified at the URLs went down, and also the reporting task can resume sending while the remote node was down, by establishing S2S connection with other available node. LGTM +1, I'm going to squash commits and merge to master. Thank you! |
Thank you for submitting a contribution to Apache NiFi.
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?
For code changes:
For documentation related changes:
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.