-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MINIFICPP-1616 Create PutAzureDatalakeStorage processor #1158
Conversation
2a42a33
to
68d1283
Compare
86eee01
to
680c70c
Compare
c62cef1
to
41275a4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly LGTM
@@ -90,14 +81,13 @@ const core::Relationship PutAzureBlobStorage::Failure("failure", "Unsuccessful o | |||
|
|||
void PutAzureBlobStorage::initialize() { | |||
// Set the supported properties | |||
setSupportedProperties({ | |||
updateSupportedProperties({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not set?
Update would make sense to me in case the base class would already set some properties, but that doesn't seem to happen as far as I see.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The base class AzureStorageProcessorBase
does set the AzureStorageCredentialsService
property beforehand in its constructor.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated in f02f86c
c8257e4
to
f02f86c
Compare
Unfortunately Azure Data Lake Storage is not supported by the Azurite docker image, so the system testing was only done manually.
https://issues.apache.org/jira/browse/MINIFICPP-1616
Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.
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 MINIFICPP-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?
For code changes:
For documentation related changes:
Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible.