Re: [VOTE] Release Apache NiFi 1.24.0 (RC5)

[Nandor Soma Abonyi]

+1 (binding)

I went through the release helper guide, connected to NiFi registry,
and imported and committed some flows.
Afterward, I verified that some simple flows ran correctly.

I've noticed that when changing a value in the parameter context that
is versioned alongside a process group, it doesn't trigger a change
event. So, if I want to commit that change, as a workaround, I have to
move something around on the canvas, and then I'm able to commit. I
vaguely remember encountering something similar in the past, but I'm
not sure if it's intended. Nevertheless, I don't see it as a critical
issue that would hold up the release.

Thanks for RM'ing Pierre!

Regards,
Soma

Pierre Villard  ezt írta (időpont: 2023.
nov. 23., Cs, 16:15):
>
> Team,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.24.0.
>
> Please review the following guide for how to verify a release candidate
> build:
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification
>
> The source being voted on the and the convenience binaries are available on
> the Apache Distribution Repository:
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.24.0
>
> The build artifacts are available on the Apache Nexus Repository:
>
> https://repository.apache.org/content/repositories/orgapachenifi-1251
>
> Git Tag: nifi-1.24.0-RC5
> Git Commit ID: 5241f434829ca46a26a475600ef7c00e1e271e37
> GitHub Commit Link:
> https://github.com/apache/nifi/commit/5241f434829ca46a26a475600ef7c00e1e271e37
>
> Checksums of nifi-1.24.0-source-release.zip
>
> SHA256: 715eb61cdc017a5f7ba4d845ae962fdf83d389829db2a8948be14f99f2cc8272
> SHA512:
> 574147002b905ef64447edec0c7308f4fc3a97b3c7f01edca05464b2b418bcd3922f956d093736014443eec88ceba36af81df37398c5fe23a1288235b79d7306
>
> Release artifacts are signed with the following key:
>
> https://people.apache.org/keys/committer/pvillard.asc
>
> KEYS file is available on the Apache Distribution Repository:
>
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> Issues resolved for this version: 285
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12353443
>
> Release note highlights can be found on the project wiki:
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.24.0
>
> The vote will be open for 72 hours.
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test. Then
> please vote:
>
> [] +1 Release this package as nifi-1.24.0
> [] +0 no opinion
> [] -1 Do not release this package because...

Re: [VOTE] Release Apache NiFi 1.23.2 (RC1)

[Nandor Soma Abonyi]

+1 (binding)

Connected to NiFi registry, imported and committed some flows.

Verified for regression:
- Azure ADLS related flows

Ran a flow to verify the fix for NIFI-11971

Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
Maven home: /usr/share/maven
Java version: 1.8.0_362, vendor: Temurin, runtime: /opt/java/openjdk/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "6.4.8-orbstack-00059-g106c60a3471f", arch: 
"aarch64", family: "unix"

Thanks for the quick turnaround all!

Regards,
Soma

> On 2023. Aug 21., at 22:16, David Handermann  
> wrote:
> 
> Team,
> 
> NOTE: This is a shortened vote window given the narrow scope of changes.
> 
> I am pleased to be calling this vote for the source release of Apache
> NiFi 1.23.2.
> 
> Please review the following guide for how to verify a release candidate build:
> 
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> 
> The source being voted on the and the convenience binaries are
> available on the Apache Distribution Repository:
> 
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.23.2
> 
> The build artifacts are available on the Apache Nexus Repository:
> 
> https://repository.apache.org/content/repositories/orgapachenifi-1235
> 
> Git Tag: nifi-1.23.2-RC1
> Git Commit ID: dec043e590f26ba2f3594f4f297dcd2b7e565ab7
> GitHub Commit Link:
> https://github.com/apache/nifi/commit/dec043e590f26ba2f3594f4f297dcd2b7e565ab7
> 
> Checksums of nifi-1.23.2-source-release.zip
> 
> SHA256: cfaa374c383a316de6d9230a0786ebe7dd97c03f8903b36365faa27bf6424fac
> SHA512: 
> a63fa624532aa3f1769013d67499caf48b9771bc3515ffca4daba2dd379722c3b25bea4519b56bc647d4e05db122e7a41519a52a703a0179b431fa881dadb4cf
> 
> Release artifacts are signed with the following key:
> 
> https://people.apache.org/keys/committer/exceptionfactory.asc
> 
> KEYS file is available on the Apache Distribution Repository:
> 
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> Issues resolved in this version: 1
> 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12353568
> 
> Release note highlights can be found on the project wiki:
> 
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.23.2
> 
> The vote will be open for 24 hours.
> 
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
> Then please vote:
> 
> [] +1 Release this package as nifi-1.23.2
> [] +0 no opinion
> [] -1 Do not release this package because...

Re: [VOTE] Release Apache NiFi 1.23.1 (RC1)

[Nandor Soma Abonyi]

+1 (binding)

Went through the release helper guide.
Connected to NiFi registry, imported and committed some flows.

Verified for regression:
- Azure ADLS and Blob_v12 related flows
- MQTT related flows

Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
Maven home: /usr/share/maven
Java version: 1.8.0_362, vendor: Temurin, runtime: /opt/java/openjdk/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "6.4.8-orbstack-00059-g106c60a3471f", arch: 
"aarch64", family: "unix"

Thanks for RM'ing David!

Regards,
Soma

> On 2023. Aug 15., at 20:06, David Handermann  
> wrote:
> 
> Team,
> 
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.23.1.
> 
> Please review the following guide for how to verify a release candidate
> build:
> 
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> 
> The source being voted upon and the convenience binaries are available on
> the Apache Distribution Repository:
> 
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.23.1/
> 
> The build artifacts are available on the Apache Nexus Repository:
> 
> https://repository.apache.org/content/repositories/orgapachenifi-1234
> 
> Git Tag: nifi-1.23.1-RC1
> Git Commit ID: f739e9dd2d476b3c0df5a806ff1dffd24be52916
> GitHub Commit Link:
> https://github.com/apache/nifi/commit/f739e9dd2d476b3c0df5a806ff1dffd24be52916
> 
> Checksums of nifi-1.23.1-source-release.zip:
> 
> SHA256: 01f5f67a9f9703232f6fe260f6c1da73f3e3a0764b8e8464f915cfad168278e6
> SHA512:
> f8a010ad5a5dd1f71fe04e5d2bf1c6637d2d0a8a7c580a0ff4dbd76c12c2e5ab4ac43e1f5314f9fca85cebe1606bd5e7ae0a8b62f577ddc68696ebd0155d
> 
> Release artifacts are signed with the following key:
> 
> https://people.apache.org/keys/committer/exceptionfactory.asc
> 
> KEYS file available here:
> 
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> 51 issues were closed/resolved for this release:
> 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12353541
> 
> Release note highlights can be found here:
> 
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.23.1
> 
> The vote will be open for 72 hours.
> 
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test. Then
> please vote:
> 
> [ ] +1 Release this package as nifi-1.23.1
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...

Re: [DISCUSS] Prepare Apache NiFi 1.23.1 Release?

[Nandor Soma Abonyi]

+1 on 1.23.1

Thanks David!

> On 2023. Aug 12., at 16:28, David Handermann  
> wrote:
> 
> Team,
> 
> Following the release of Apache NiFi 1.23.0, several important bugs have
> been resolved in a few Processors [1], and there have been a handful of
> incremental dependency upgrades [2]. Preparing an incremental patch release
> would provide the opportunity to incorporate these bug fixes and pull in a
> selected number of dependency upgrades.
> 
> I am willing to handle the Release Manager responsibilities. If there is a
> positive response to this approach, I can put together a selected list of
> issues next week.
> 
> Regards,
> David Handermann
> 
> [1]
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20NIFI%20AND%20issuetype%20%3D%20Bug%20AND%20fixVersion%20%3D%201.24.0
> 
> [2]
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20NIFI%20AND%20fixVersion%20%3D%201.24.0

Re: NiFi Issue

[Nandor Soma Abonyi]

Hi,

HandleHttpResponse is designed to be used in conjunction with 
HandleHttpRequest. Based on the description,
it seems like InvokeHTTP’s Response connection has been connected to 
HandleHttpResponse, which is not needed
because the output FlowFile on the Response connection already contains the API 
response.

Br,
Nandor

> On 2023. Aug 10., at 22:46, Mark Payne  wrote:
> 
> Hi Sagar,
> 
> Can you share more about how your flow is setup?
> 
> It sounds like the flow is maybe attempting to send a response to the same 
> message multiple times,
> or the request is timing out while the data is flowing through NiFi.
> 
> Thanks
> -Mark
> 
>> On Aug 10, 2023, at 3:18 PM, Sagar Reddy Poreddy  
>> wrote:
>> 
>> Dear NiFi Team,
>> 
>> Hope you are doing well, I would like report and issue that I am facing
>> with NiFi HandleHttpResponse. I have an SAP API, I am consuming it via
>> invokeHttp and connected the response to HandleHttpResponse. When I call
>> the api for the first time it is giving the correct response (via
>> invokeHttp url) , however after that it is returning "Could not find HTTP
>> response object for this identifier". I am getting the same error message
>> in NiFi 1.18.0 and 1.19.1, Can you please tell me if it is fixed in any
>> other version or else please give me a solution.
>> 
>> Thanks,
>> Sagar Reddy
> 

Re: [VOTE] Release Apache NiFi 1.23.0 (RC3)

[Nandor Soma Abonyi]

+1 (binding)

Went through the release helper guide.
Connected to NiFi registry, imported and committed some flows.

Verified new features:
- NIFI-11758 Add local file upload option in PutAzure*Storage processors

Verified for regression:
- Azure ADLS and Blob_v12 related flows
- MQTT related flows

Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
Maven home: /usr/share/maven
Java version: 1.8.0_362, vendor: Temurin, runtime: /opt/java/openjdk/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "6.3.12-orbstack-00210-ga4f4fae8883e", arch: 
"aarch64", family: "unix"

Thanks for RM'ing David!

Regards,
Soma

> On 2023. Jul 25., at 23:32, David Handermann  
> wrote:
> 
> Team,
> 
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.23.0.
> 
> Please review the following guide for how to verify a release candidate
> build:
> 
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> 
> The source being voted upon and the convenience binaries are available on
> the Apache Distribution Repository:
> 
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.23.0/
> 
> The build artifacts are available on the Apache Nexus Repository:
> 
> https://repository.apache.org/content/repositories/orgapachenifi-1233
> 
> Git Tag: nifi-1.23.0-RC3
> Git Commit ID: 27a690a30a6ae77c217a47ac0601e85970777ca2
> GitHub Commit Link:
> https://github.com/apache/nifi/commit/27a690a30a6ae77c217a47ac0601e85970777ca2
> 
> Checksums of nifi-1.23.0-source-release.zip:
> 
> SHA256: 39c97d89804b005cc995c56a87a3df6f68c44ee42114dffe756bbac90a3593cf
> SHA512:
> f256ca731a67435e9883626931abc58f28cda9deb6a7d0a84ed97b78104e43b3b638ee2297d79f92bf5a1e19f62cc78e0a886fa0094593ab34b21d658c59eadd
> 
> Release artifacts are signed with the following key:
> 
> https://people.apache.org/keys/committer/exceptionfactory.asc
> 
> KEYS file available here:
> 
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> 132 issues were closed/resolved for this release:
> 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12353320
> 
> Release note highlights can be found here:
> 
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.23.0
> 
> The vote will be open for 72 hours.
> 
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test. Then
> please vote:
> 
> [ ] +1 Release this package as nifi-1.23.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...

Re: [ANNOUNCE] New nifi PMC Member Nandor Soma Abonyi

[Nandor Soma Abonyi]

Thank you, everyone! This is a fantastic community, and great to be part of it!

Joe Witt  ezt írta (időpont: 2023. jún. 27., K, 1:11):
>
> On behalf of the Apache NiFI PMC, I am very pleased to announce that Nandor
> has accepted the PMC's invitation to join the Apache NiFi PMC. We greatly
> appreciate the PR reviews and code contributions and release management
> work of Nandor.
>
> Please join us in congratulating and welcoming Nandor to the Apache NiFi
> PMC.
>
> Congratulations Nandor!

[ANNOUNCE] Apache NiFi NAR Maven Plugin 1.5.1 release

[Nandor Soma Abonyi]

Hello

The Apache NiFi team would like to announce the release of Apache NiFi NAR
Maven Plugin 1.5.1.

Apache NiFi is an easy to use, powerful, and reliable system to process and
distribute
data.  Apache NiFi was made for dataflow.  It supports highly configurable
directed graphs
of data routing, transformation, and system mediation logic.

Nar Maven Plugin is a release artifact used for supporting the NiFi
classloader isolation model.

More details on Apache NiFi can be found here:
https://nifi.apache.org/

The release artifacts can be downloaded from here:
https://repository.apache.org/content/groups/public/org/apache/nifi/nifi-nar-maven-plugin/1.5.1/

Maven artifacts have been made available and mirrored as per normal ASF
artifact processes.

Issues closed/resolved for this list can be found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12353009

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiNARMavenPluginVersion1.5.1

Thank you
The Apache NiFi team

[RESULT][VOTE] Release Apache NiFi NAR Maven Plugin 1.5.1

[Nandor Soma Abonyi]

Apache NiFi Community,

I am pleased to announce that the 1.5.1 release of Apache NiFi NAR Maven Plugin 
passes with
5 +1 (binding) votes
2 +1 (non-binding) votes
0 0 votes
0 -1 votes

Thanks to all who helped make this release possible. Especially thanks to Kevin 
Doran, who
guided me through the process. As a first-time RM, it was so valuable.

Here is the PMC vote thread: 
https://lists.apache.org/thread/vrr3ndjh2wd9f4c8slb82232yglbfysd

Re: [VOTE] Release Apache NiFi NAR Maven Plugin 1.5.1

[Nandor Soma Abonyi]

+1 (non-binding)

> On 2023. Jun 15., at 0:53, Nandor Soma Abonyi  wrote:
> 
> Hello Apache NiFi Community,
> 
> I am pleased to be calling this vote for the source release of Apache NiFi 
> NAR Maven Plugin 1.5.1.
> 
> The source being voted upon, including signatures, digests, etc. can be found 
> at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-nar-maven-plugin-1.5.1/
> 
> A helpful reminder on how the release candidate verification process works:
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+NAR+Maven+Plugin+release+candidate
> 
> The Git tag is nifi-nar-maven-plugin-1.5.1-rc1
> The Git commit ID is 39fc959426ea405df6360969b55ae2adad47e1aa
> https://gitbox.apache.org/repos/asf?p=nifi-maven.git;a=commit;h=39fc959426ea405df6360969b55ae2adad47e1aa
> 
> Checksums of nifi-nar-maven-plugin-1.5.1-source-release.zip:
> SHA256: 0ddc4efbfe504f9ed6477b8c572f2c6e5ba0c953e2e5b063bdfbd1f934eda6bf
> SHA512: 
> a7281c8a3769db37e3491f3a5e54533b5f26bdcad99f8adb1e5609f1de17309aefb3d49eb9231e75a814e42566525b9afe4a11bda2c4ab48e8bab5a298b72b24
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/nsabonyi.asc
> 
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> 3 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12353009
> 
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiNARMavenPluginVersion1.5.1
> 
> The vote will be open for 72 hours. Please download the release
> candidate and evaluate the necessary items including checking hashes,
> signatures, build from source, and test. Then please vote:
> 
> [ ] +1 Release this package as nifi-nar-maven-plugin-1.5.1
> [ ] +0 no opinion
> [ ] -1 Do not release this package because …
> 

Re: New API Security Custom Processors

[Nandor Soma Abonyi]

Dear Bryce,

Thank you for reaching out and expressing your interest in contributing to 
Apache NiFi! We greatly appreciate
your effort and enthusiasm to share your code with the community. We welcome 
contributions from developers
like you who help enhance the capabilities of our project.

To ensure a smooth process for submitting your code changes, we have a few 
guidelines in place. Firstly,
please open a Jira ticket to provide a description of the changes you have made 
and the motivation behind them.
This ticket will serve as a central point for discussions and feedback on your 
contribution.
In order to open a Jira ticket, you will need assistance from a Project 
Management Committee (PMC) member who
can grant you Jira contributor access. You can reach out to any PMC member, who 
will be happy to assist you.

Furthermore, we encourage you to submit a GitHub pull request (PR) for your 
code changes. While there are
plenty of guides available on the internet on how to open a GitHub pull 
request, you may find it useful to
refer to our own contributor guide located at: 
https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide
This guide provides detailed instructions and best practices for submitting a 
pull request to Apache NiFi's GitHub repository.

Once your pull request is submitted, our community of developers will review 
your code, provide feedback,
and work with you to ensure the quality and compatibility of your contribution. 
Collaboration and iteration are
key aspects of our open-source development process, and we appreciate your 
willingness to engage in this manner.

If you have any questions or need further assistance, please don't hesitate to 
ask.

Thank you again for your willingness to contribute.

Best regards,
Nandor Soma Abonyi


> On 2023. Jun 15., at 4:03,   wrote:
> 
> Hi Nifi Dev Team
> 
> 
> 
> I am new to the open source community and not really a developer, but have
> developed 2 Nifi Customs processors to improve its support for APIs and API
> Security.  Looking for some help from more experienced Nifi contributors to
> review the code, and if appropriate contribute it to the base product. The
> processors are.
> 
> 
> 
> 1.OAuth 2.0 JWT Token Validation Processor. Uses the RSA 256 Public
> Key to validate the JWT signature then can optionally validate the Issuer
> and Client ID, and if the Token is valid, extract claims into FlowFile
> attributes based on a list provided to the processor. The full JWT decoded
> claim (JSON) is also added as an attribute.  If the token has expired or is
> invalid, details of the error are available in attributes for error
> handling.
> 2.OAS 3.0 API Validation Processor.  Accepts the Swagger API URL (OAS
> JSON) to validate the HTTP Request against the API definition. If valid, it
> will extract an URI Parms and URL Query Parms to FlowFile Attributes, as
> well as the specific API interface operationId, which can then be use by the
> RouteOnAttribute processor to pass each API interface to separate flow for
> processing. If the request is invalid, details of the error are available in
> attributes for error handling.
> 
> 
> 
> I am happy to provide the code and usage examples to anyone that would like
> to validate the code and submit is for inclusion into the core Nifi product;
> Thanks.
> 
> 
> 
> Kind Regards
> 
> 
> 
> Bryce Macdonald
> 
> 
> 
> 
> 

[VOTE] Release Apache NiFi NAR Maven Plugin 1.5.1

[Nandor Soma Abonyi]

Hello Apache NiFi Community,

I am pleased to be calling this vote for the source release of Apache NiFi NAR 
Maven Plugin 1.5.1.

The source being voted upon, including signatures, digests, etc. can be found 
at:
https://dist.apache.org/repos/dist/dev/nifi/nifi-nar-maven-plugin-1.5.1/

A helpful reminder on how the release candidate verification process works:
https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+NAR+Maven+Plugin+release+candidate

The Git tag is nifi-nar-maven-plugin-1.5.1-rc1
The Git commit ID is 39fc959426ea405df6360969b55ae2adad47e1aa
https://gitbox.apache.org/repos/asf?p=nifi-maven.git;a=commit;h=39fc959426ea405df6360969b55ae2adad47e1aa

Checksums of nifi-nar-maven-plugin-1.5.1-source-release.zip:
SHA256: 0ddc4efbfe504f9ed6477b8c572f2c6e5ba0c953e2e5b063bdfbd1f934eda6bf
SHA512: 
a7281c8a3769db37e3491f3a5e54533b5f26bdcad99f8adb1e5609f1de17309aefb3d49eb9231e75a814e42566525b9afe4a11bda2c4ab48e8bab5a298b72b24

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/nsabonyi.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/nifi/KEYS

3 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12353009

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiNARMavenPluginVersion1.5.1

The vote will be open for 72 hours. Please download the release
candidate and evaluate the necessary items including checking hashes,
signatures, build from source, and test. Then please vote:

[ ] +1 Release this package as nifi-nar-maven-plugin-1.5.1
[ ] +0 no opinion
[ ] -1 Do not release this package because …

Re: [DISCUSS] Release NiFi NAR Maven Plugin 1.5.1

[Nandor Soma Abonyi]

Thank you for the feedback!

I will soon initiate the voting process.

> On 2023. Jun 13., at 19:16, Krisztina Zsihovszki  wrote:
> 
> +1,
> I support the idea as well.
> 
> Thanks for RMing, Nandor!
> 
> On Tue, Jun 13, 2023 at 6:57 PM Matt Burgess  wrote:
> 
>> +1 from me, I ran into the issue so would like to have that fix
>> available.  Thanks for volunteering to RM!
>> 
>> On Mon, Jun 12, 2023 at 5:36 AM Nandor Soma Abonyi
>>  wrote:
>>> 
>>> Hello Apache NiFi Community,
>>> 
>>> I'd like to initiate a discussion about the next release of
>> nifi-nar-maven-plugin.
>>> 
>>> Currently, nifi-nar-maven-plugin doesn’t use remote repositories, which
>> was
>>> fixed in [1]. Though it is the only change since the last release, I
>> consider it significant
>>> enough to suggest releasing nifi-nar-maven-plugin as 1.5.1.
>>> 
>>> I would be happy to take on RM duties for this release.
>>> 
>>> Do you agree it is time for a new release?
>>> 
>>> Thanks,
>>> Nandor Soma Abonyi
>>> 
>>> [1] NIFI-11324 <https://issues.apache.org/jira/browse/NIFI-11324> NAR
>> Plugin extension docs not correctly resolving overridden versions from
>> system properties
>>> 
>> 

[DISCUSS] Release NiFi NAR Maven Plugin 1.5.1

[Nandor Soma Abonyi]

Hello Apache NiFi Community,

I'd like to initiate a discussion about the next release of 
nifi-nar-maven-plugin.

Currently, nifi-nar-maven-plugin doesn’t use remote repositories, which was
fixed in [1]. Though it is the only change since the last release, I consider 
it significant
enough to suggest releasing nifi-nar-maven-plugin as 1.5.1.

I would be happy to take on RM duties for this release.

Do you agree it is time for a new release?

Thanks,
Nandor Soma Abonyi

[1] NIFI-11324 <https://issues.apache.org/jira/browse/NIFI-11324> NAR Plugin 
extension docs not correctly resolving overridden versions from system 
properties

Re: [VOTE] Release Apache NiFi 1.22.0 (RC1)

[Nandor Soma Abonyi]

+1 (non-binding)

Went through the release helper guide.
Connected to NiFi registry, imported and committed some flows.

Verified for regression:
- Azure ADLS and Blob_v12 related flows
- MQTT related flows

Noticed two issues:
- Sometimes `./bin/nifi.sh start --wait-for-init` incorrectly reports that 
"NiFi is not running. Stopped waiting for it to initialize.” while it was 
started successfully.
  I don’t consider it a blocker, will try to investigate it further.
- In ConsumeMQTT when `Add attributes as fields` is true and using 
AvroRecordSetWriter, the appended field values are null. While they have the 
correct values when using JsonRecordSetWriter.
  Checked with older versions and it is a long standing issue, hence I don’t 
consider it as a blocker. Opened a Jira to track it. [1]

Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
Java version: 1.8.0_362, vendor: Temurin
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "6.3.4-orbstack-00151-g5c9dc5b64d8c", arch: 
"aarch64", family: "unix

Thanks for RM'ing Joe!

Regards,
Soma

[1] https://issues.apache.org/jira/browse/NIFI-11662


> On 2023. Jun 6., at 23:38, Joe Witt  wrote:
> 
> Hello,
> 
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.22.0.
> 
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1228
> 
> The source being voted upon and the convenience binaries can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.22.0/
> 
> A helpful reminder on how the release candidate verification process works:
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> 
> The Git tag is nifi-1.22.0-RC1
> The Git commit ID is 71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8
> https://github.com/apache/nifi/commit/71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8
> 
> Checksums of nifi-1.22.0-source-release.zip:
> SHA256: d63a5f1db95160434670f112a0ee6e06fa141182bd0f12f0e58e3229991f3743
> SHA512:
> 5f6da64e75a2d5446f1f274fe3de7e97290f5b916eabbc0491a99c6db33f74fbdea001b403044e75bc5c2183fb0500dfc143d0f4cba19d3511f866fff774d7f5
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
> 
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> 186 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12353069
> 
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.22.0
> 
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> from source, and test. Then please vote:
> 
> [ ] +1 Release this package as nifi-1.22.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...

Re: Multiple topic with ConsumeMQTT processor

[Nandor Soma Abonyi]

Dear Chandradeep,

Though I haven't seen your configuration yet, I tried to test the scenario. If 
you want to listen to different topics with a single processor, you need to use 
wildcards. If you have two clients that are publishing to 
buildings/A/1/temperature and buildings/A/2/temperature, then the subscriber 
client’s topic filter should be buildings/A/+/temperature. With the latest 
version (1.21.0) this works as expected. I’ve also tested the “workaround” 
approach to create two consumers but it also worked correctly. I advise you to 
revise your configuration. If you need additional help, please share it on the 
user's mailing list or through the NiFi Slack channel.

Best regards,
Nandor Soma Abonyi

> On May 6, 2023, at 2:28 PM, Nandor Soma Abonyi  
> wrote:
> 
> Dear Chandradeep,
> 
> It seems like the images didn’t go through.
> Could you attach them again?
> 
> Best regards,
> Nandor Soma Abonyi
> 
>> On 2023. May 6., at 13:59, Chandradeep Kumar 
>>  wrote:
>> 
>> 
>> Dear Dev,
>> 
>> I’m trying to handle a scenario where more than one topic could be able to 
>> subscribe to a MQTT Broker via ConsumeMQTT processor.
>> 
>> Currently I’m able to subscribe single topic and receive message which is 
>> published on same topic.
>> 
>> Below configuration of ConsumeMQTT works fine:
>> 
>> 
>> But when I configured more than one topic in this processor then it is not 
>> working:
>> 
>> 
>> 
>> When I tried to create two consumeMQTT processor which are connected with 
>> single funnel then both are not working. However when I stopped anyone then 
>> its started working.
>> 
>> Request you to kindly help me out on this use case.
>> Thanks in advance.
>> 
>> Regards,
>> Chandradeep
>> The contents of this e-mail and any attachment(s) are confidential and 
>> intended for the named recipient(s) only. It shall not attach any liability 
>> on the originator or NEC Corporation India Private Limited or its 
>> affiliates. Any views or opinions presented in this email are solely those 
>> of the author and may not necessarily reflect the opinions of NEC 
>> Corporation India Private Limited or its affiliates. Any form of 
>> reproduction, dissemination, copying, disclosure, modification, distribution 
>> and / or publication of this message without the prior written consent of 
>> the author of this e-mail is strictly prohibited. If you have received this 
>> email in error please delete it and notify the sender immediately.

Re: Multiple topic with ConsumeMQTT processor

[Nandor Soma Abonyi]

Dear Chandradeep,

Though I haven't seen your configuration yet, I tried to test the scenario. If 
you want to listen to different topics with a single processor, you need to use 
wildcards. If you have two clients that are publishing to 
buildings/A/1/temperature and buildings/A/2/temperature, then the subscriber 
client’s topic filter should be buildings/A/+/temperature. With the latest 
version (1.21.0) this works as expected. I’ve also tested the “workaround” 
approach to create two consumers but it also worked correctly. I advise you to 
revise your configuration. If you need additional help, please share it on the 
user's mailing list or through the NiFi Slack channel.

Best regards,
Nandor Soma Abonyi

> On May 6, 2023, at 2:28 PM, Nandor Soma Abonyi  
> wrote:
> 
> Dear Chandradeep,
> 
> It seems like the images didn’t go through.
> Could you attach them again?
> 
> Best regards,
> Nandor Soma Abonyi
> 
>> On 2023. May 6., at 13:59, Chandradeep Kumar 
>>  wrote:
>> 
>> 
>> Dear Dev,
>> 
>> I’m trying to handle a scenario where more than one topic could be able to 
>> subscribe to a MQTT Broker via ConsumeMQTT processor.
>> 
>> Currently I’m able to subscribe single topic and receive message which is 
>> published on same topic.
>> 
>> Below configuration of ConsumeMQTT works fine:
>> 
>> 
>> But when I configured more than one topic in this processor then it is not 
>> working:
>> 
>> 
>> 
>> When I tried to create two consumeMQTT processor which are connected with 
>> single funnel then both are not working. However when I stopped anyone then 
>> its started working.
>> 
>> Request you to kindly help me out on this use case.
>> Thanks in advance.
>> 
>> Regards,
>> Chandradeep
>> The contents of this e-mail and any attachment(s) are confidential and 
>> intended for the named recipient(s) only. It shall not attach any liability 
>> on the originator or NEC Corporation India Private Limited or its 
>> affiliates. Any views or opinions presented in this email are solely those 
>> of the author and may not necessarily reflect the opinions of NEC 
>> Corporation India Private Limited or its affiliates. Any form of 
>> reproduction, dissemination, copying, disclosure, modification, distribution 
>> and / or publication of this message without the prior written consent of 
>> the author of this e-mail is strictly prohibited. If you have received this 
>> email in error please delete it and notify the sender immediately.

Re: Multiple topic with ConsumeMQTT processor

[Nandor Soma Abonyi]

Dear Chandradeep,

It seems like the images didn’t go through.
Could you attach them again?

Best regards,
Nandor Soma Abonyi

> On 2023. May 6., at 13:59, Chandradeep Kumar 
>  wrote:
> 
> 
> Dear Dev,
>  
> I’m trying to handle a scenario where more than one topic could be able to 
> subscribe to a MQTT Broker via ConsumeMQTT processor.
>  
> Currently I’m able to subscribe single topic and receive message which is 
> published on same topic.
>  
> Below configuration of ConsumeMQTT works fine:
> 
>  
> But when I configured more than one topic in this processor then it is not 
> working:
>  
> 
>  
> When I tried to create two consumeMQTT processor which are connected with 
> single funnel then both are not working. However when I stopped anyone then 
> its started working.
>  
> Request you to kindly help me out on this use case.
> Thanks in advance.
>  
> Regards,
> Chandradeep
> The contents of this e-mail and any attachment(s) are confidential and 
> intended for the named recipient(s) only. It shall not attach any liability 
> on the originator or NEC Corporation India Private Limited or its affiliates. 
> Any views or opinions presented in this email are solely those of the author 
> and may not necessarily reflect the opinions of NEC Corporation India Private 
> Limited or its affiliates. Any form of reproduction, dissemination, copying, 
> disclosure, modification, distribution and / or publication of this message 
> without the prior written consent of the author of this e-mail is strictly 
> prohibited. If you have received this email in error please delete it and 
> notify the sender immediately.

Re: [VOTE] Release Apache NiFi 1.21.0 (RC2)

[Nandor Soma Abonyi]

+1 (non-binding)

Went through the release helper guide.
Connected to NiFi registry, imported and committed some flows.

Verified these issues:
- NIFI-11137 Add record support to Consume/PublishJMS
- NIFI-11173 Add default values to DeleteAzureBlobStorage_v12
- NIFI-11264 Improve logging in list processors and fix ListFile's description

Verified for regression:
- Azure ADLS and Blob_v12 related flows
- MQTT related flows

Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
Java version: 1.8.0_362, vendor: Temurin
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "6.1.22-orbstack-00101-gc15df7c38de4", arch: 
"amd64", family: "unix"

Thanks for RM'ing Joe!

Regards,
Soma

> On Apr 4, 2023, at 2:10 AM, Joe Witt  wrote:
> 
> Hello,
> 
> I am pleased to be calling this vote for the source release of Apache
> NiFi 1.21.0.
> 
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1226
> 
> The source being voted upon and the convenience binaries can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.21.0/
> 
> A helpful reminder on how the release candidate verification process works:
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> 
> The Git tag is nifi-1.21.0-RC2
> The Git commit ID is 892f822107da84ca0dcfefdb5c91c5bc11dc3dc1
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=892f822107da84ca0dcfefdb5c91c5bc11dc3dc1
> 
> Checksums of nifi-1.21.0-source-release.zip:
> SHA256: 598bf8e90f871f4ca25709dd4ecf3da16c814c08c0d8b2c8744dbd34df34dea5
> SHA512: 
> 58c10976bc22fb5406d9d1d9b7ca7d90c2dbed99565d00f1172bb33b375e9e068da5003d9dbbd87d2b17626e4e310b999c8581718532934e855c2134be763f04
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
> 
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> 126 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12352899
> 
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.21.0
> 
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> from source, and test. Then please vote:
> 
> [ ] +1 Release this package as nifi-1.21.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...

Re: [discuss] NiFi support for Hadoop ecosystem components

[Nandor Soma Abonyi]

Thank you for raising this topic, Joe!

While I understand the desire to remove Hadoop components, I have mixed
feelings about removing one of the core parts of the Big Data world from the
project. I'm unsure for how many users we could make a hard time removing
those components. It seems to be a too significant shift in our philosophy.
We can already see in the above example that somebody would not use
NiFi if we'd removed them.

Furthermore, although Hadoop has been buried multiple times, new technologies
seem to still depend on it. For example, Iceberg, in which case I'm worried 
about
the consequences of removing the support for an increasingly popular technology.

So I wonder whether it is possible to find a forward-looking solution that could
serve all projects. I've always found configuring Hadoop and friends too tricky
and I thought it was primarily for historical reasons. The issues you describe 
could
easily result from such a thing. I assume that over time, new and new things 
have
been added on top of the existing implementation without significant 
refactoring.

My - probably utopistic - idea would be to contact the Hadoop and Hive teams
and share the issues we are dealing with. Probably we are not alone in these
problems, but I don't know whether they are aware of them. Even if they are,
I think approaching them is worth the chance. Who knows where we will end up
if somebody representing the NiFi project does that?

Regards,
Nandor Soma Abonyi


> On Mar 24, 2023, at 10:40 PM, Jeremy Dyer  wrote:
> 
> I think option 2 is the best way to handle this.
> 
> Technology naturally changes over time and some components of Nifi might not 
> make the most sense to keep around in the main line for the masses anymore. 
> However I really like still having them there for people to very simply add 
> if they so desire too. I see other platforms do this by adding a “contrib” 
> repo. What if we had something like a “nifi-contrib” or “nifi-emeritus” repo 
> in GitHub, Apache GitHub repo, where the community can still be involved as 
> desired but also keep things readily available to those who might not even be 
> heavily involved in the community?
> 
> I even see this as a sustainable pattern for any components that need “moved 
> out”.
> 
> I wouldn’t even think those components in the “contrib” repo would require 
> voting on for releases but someone, or a vendor, could update them via PRs 
> after the official release.
> 
> Jeremy Dyer
> 
> Get Outlook for iOS<https://aka.ms/o0ukef>
> 
> From: Chakravarty, G 
> Sent: Friday, March 24, 2023 4:36:43 PM
> To: dev@nifi.apache.org 
> Subject: Re: [discuss] NiFi support for Hadoop ecosystem components
> 
> I am wondering if the standard Nifi jdbc/odbc processors with some basic 
> testing with the common drivers like Simba etc. Hive drivers can help to 
> alleviate the issue without having separate HiveQL processors.
> 
> GC
> 
> From: Bryan Bende 
> Sent: Friday, March 24, 2023 4:05 PM
> To: dev@nifi.apache.org 
> Subject: Re: [discuss] NiFi support for Hadoop ecosystem components
> 
> I lean towards option 2 with the caveat that maybe we don't have to
> retain every Hadoop related component when creating this separate set
> of components. Mainly I'm thinking that Hive has been the most
> problematic to maintain so maybe that is dropped all together. I think
> it would be unfortunate to not have publicly available HDFS
> processors.
> 
> On Fri, Mar 24, 2023 at 3:23 PM Matt Burgess  wrote:
>> 
>> As one of the small number of people that fight the battle, I like the
>> idea of Option 1 (full disclosure: I work for a vendor). From a
>> community standpoint (I'm on the PMC) I'm not strongly opposed to
>> Option 2 although I wouldn't want to be the one managing and releasing
>> the artifacts :) Having said that, unless it remained maintained and
>> released, I feel like it would just be a component graveyard (or maybe
>> more like the Apache Attic), in which case it seems unnecessary and
>> that's why I'm behind Option 1. Interested to hear others' thoughts of
>> course.
>> 
>> Thanks,
>> Matt
>> 
>> On Fri, Mar 24, 2023 at 2:07 PM Joe Witt  wrote:
>>> 
>>> Team,
>>> 
>>> For the full time NiFi has been in Apache we've built with support for
>>> various Hadoop ecosystem components like HDFS, Hive, HBase, others,
>>> and more recently formats/serialization modes like necessary for
>>> Parquet, Orc, Iceberg, etc..
>>> 
>>> All of these things however present endless challenges with
>>> compatibility acros

Re: [VOTE] Release Apache NiFi NAR Maven Plugin 1.5.0 - RC2

[Nandor Soma Abonyi]

+1 (non-binding)

- Verified hashes and signatures
- Compiled the provided source
- Compiled NiFi main with nifi-nar-maven-plugin:1.5.0

Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Java version: 11.0.18, vendor: Eclipse Adoptium
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "13.1", arch: "x86_64", family: “mac”

Thanks for RM’ing Kevin!

Regards,
Soma

> On Mar 14, 2023, at 9:59 PM, Kevin Doran  wrote:
> 
> Hello Apache NiFi Community,
> 
> Issues with RC1 have been addressed in RC2, and I am pleased to again
> be calling this vote for the source release of Apache NiFi NAR Maven
> Plugin 1.5.0.
> 
> The source being voted upon, including signatures, digests, etc. can
> be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1222/org/apache/nifi/nifi-nar-maven-plugin/1.5.0/
> 
> The Git tag is nifi-nar-maven-plugin-1.5.0-RC2
> The Git commit ID is 277f9e8998ca76a972c90d8ecf3f771414c86700
> https://gitbox.apache.org/repos/asf?p=nifi-maven.git;a=commit;h=277f9e8998ca76a972c90d8ecf3f771414c86700
> 
> Checksum of nifi-nar-maven-plugin-1.5.0-source-release.zip:
> 
> SHA512: 
> a265587f8bfb31359cae2335394d88d76d36ae9806030e38fc9846264f20a4e70d642c4f0c08425b843794aaabaeea416b1104ede26671ffcbe001e1976d4efd
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/kdoran.asc
> 
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> 4 issues were closed/resolved for this release:
> https://issues.apache.org/jira/projects/NIFI/versions/12352895
> 
> Release note highlights can be found here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12352895
> 
> *The vote will be open for 24 hours.* Please download the release
> candidate and evaluate the necessary items including checking hashes,
> signatures, build from source, and test. Then please vote:
> 
> [ ] +1 Release this package as nifi-nar-maven-plugin-1.5.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...

Re: [VOTE] Release Apache NiFi 1.20.0 (RC1)

[Nandor Soma Abonyi]

+1 (non-binding)

Went through the release helper guide.
Connected to NiFi registry, imported and committed some flows.
Verified these new issues:
- NIFI-10991 - Add AWS MSK IAM support to Kafka processors
- NIFI-11107 - ConsumeIMAP and ConsumePOP3 with OAUTH
Verified for regression:
- Azure ADLS and Blob_v12 related flows

Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Java version:
- 1.8.0_332, vendor: Temurin
- 11.0.18, vendor: Eclipse Adoptium
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "13.1", arch: "x86_64", family: “mac”

Thanks for RM'ing Joe!

Regards,
Soma

> On Feb 6, 2023, at 9:54 PM, Joe Witt  wrote:
> 
> Hello,
> 
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.20.0.
> 
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1220
> 
> The source being voted upon and the convenience binaries can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.20.0/
> 
> A helpful reminder on how the release candidate verification process works:
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> 
> The Git tag is nifi-1.20.0-RC1
> The Git commit ID is 81296b5b69a69d26afb8f8dec3a58a8363653890
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=81296b5b69a69d26afb8f8dec3a58a8363653890
> 
> Checksums of nifi-1.20.0-source-release.zip:
> SHA256: 694e9eec951caf628576a2aaa16e7ddadc11b9bf455f16d503bdd88aefdbfe66
> SHA512:
> f54891aadbf58eaf4df465e99eb935ddbb47c70c1e329968098762f670eeed56a427ed88f21f150c056f8b057f7120127f3470afe4f4f89b80d659d7b8080339
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
> 
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> 205 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12352581
> 
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.20.0
> 
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> from source, and test. Then please vote:
> 
> [ ] +1 Release this package as nifi-1.20.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...

Re: nifi proxy issue + jira account

[Nandor Soma Abonyi]

Hi Kyle!

Regarding your question using StandardOauth2AccessTokenProvider with a proxy. 
The standard NiFi way is to use an implementation of ProxyConfigurationService 
(link 
)
 to configure a proxy. If a component doesn’t have Proxy Configuration Service 
property, it means that it doesn’t supports using a proxy officially. I’m 
saying “officially” because the underlying library that we use (in our case 
OkHttp) may respect environment variables, but it is out of our hands and I 
wouldn’t rely on that. Here 

 is an example of a processor which supports proxying. As you already 
mentioned, I’d also request this feature through Jira.

Regards,
Nandor

> On Dec 16, 2022, at 5:19 AM, Matt Burgess  wrote:
> 
> Kyle,
> 
> Per the new Apache Jira instructions [1], please provide the following
> information to priv...@nifi.apache.org  
> mailto:priv...@apache.org>> and I can
> create an account for you and add you as a
> contributor:
> 
> - email address
> - preferred username (N.B. hyphens not allowed)
> - alternate username (in case the preferred one is already in use)
> - display name, if it is different from the username
> 
> 
> Regards,
> Matt
> 
> [1] https://infra.apache.org/jira-guidelines.html#who 
> 
> 
> On Thu, Dec 15, 2022 at 4:43 PM Nguyen, Kyle  >
> wrote:
> 
>> Hi. Thanks for maintaining the project.
>> 
>> 
>> 
>> 1. Can I get a jira account please? Would like to request *
>> StandardProxyConfigurationService* integration into 
>> *StandardOath2AccessTokenProvider
>> *and into *QuerySalesforceObject*
>> 
>> 2. Or perhaps you can help me more directly on this stackoverflow:
>> https://stackoverflow.com/questions/74482819/connecting-to-an-external-http-api-behind-a-proxy-from-nifi
>> 
>> 
>> 
>> I also tried this ENV VAR in my docker nifi instance. It doesn’t work.
>> 
>> 
>> 
>> JAVA_FLAGS=-Dhttp.nonProxyHosts="localhost,.amazonaws.com"
>> -Dhttp.proxyHost=proxy.foo.com -Dhttp.proxyPort=3128 -Dhttp.proxyUser=foo
>> -Dhttp.proxyPassword=bar
>> 
>> 
>> 
>> 
>> 
>> [image: cid:17261f6184a4cff311 ]
>> 
>> *Kyle Nguyen*
>> Corporate Technology, Software Engineer
>> 
>> 
>> 
>> *Millennium Management LLC*
>> 
>> 399 Park Avenue | New York, NY 10022
>> 
>> 📞 +1.212.708.1366 | 📱 +1.929.837.1788
>> 
>> mlp.com  > >
>> 
>> 
>> 
>> 
>> 
>> ##
>> 
>> The information contained in this communication is confidential and
>> 
>> may contain information that is privileged or exempt from disclosure
>> 
>> under applicable law. If you are not a named addressee, please notify
>> 
>> the sender immediately and delete this email from your system.
>> 
>> If you have received this communication, and are not a named
>> 
>> recipient, you are hereby notified that any dissemination,
>> 
>> distribution or copying of this communication is strictly prohibited.
>> ##

Re: [VOTE] Adopt NiFi 2.0 Proposed Release Goals

[Nandor Soma Abonyi]

+1 (non-binding)

> On Dec 12, 2022, at 6:02 PM, David Handermann  
> wrote:
> 
> Team,
> 
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt the following
> as Release Goals for NiFi 2.0:
> 
> 1. Remove Java 8 support and require Java 11
> 2. Remove deprecated components
> 3. Remove deprecated component properties
> 4. Remove components integrating with unmaintained services
> 5. Remove compatibility classes and methods
> 6. Remove flow.xml.gz in favor of flow.json.gz
> 7. Remove duplicative features
> 8. Upgrade internal Java API references
> 9. Reorganize standard components
> 10. Implement migration tools for upgrading flows
> 
> A positive vote indicates agreement on these goals and the initiation of
> the following actions:
> 
> 1. Rename NiFi 2.0 Proposed Release Goals to NiFi 2.0 Release Goals
> 2. Create version 1 branch in Git for subsequent support releases on the
> version 1 series
> 3. Update the current main branch in Git to version 2.0.0-SNAPSHOT
> 
> The vote will be open for 72 hours and follow standard procedures for
> release votes.
> 
> Please review the linked goals and discussions for background.
> 
> [ ] +1 Adopt NiFi 2.0 Release Goals
> [ ] +0 No opinion
> [ ] -1 Do not adopt NiFi 2.0 Release Goals for the following reasons...
> 
> [1]
> https://cwiki.apache.org/confluence/display/NIFI/NiFi+2.0+Proposed+Release+Goals
> [2] https://lists.apache.org/thread/xo77p9t3xg4k70356xrqbdg4m9sg7sf8

Re: [VOTE] Release Apache NiFi 1.19.1 (RC2)

[Nandor Soma Abonyi]

+1 (non-binding)

- Went through the release helper guide.
- Tested interaction with NiFi registry.
- Ran a simple flow to verify NIFI-10785.
- Verified NIFI-10872.

Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Java version: 1.8.0_332, vendor: Temurin
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"

Thanks for RM'ing Joe!
Regards,
Soma

> On Dec 5, 2022, at 8:57 PM, Joe Witt  wrote:
> 
> Hello,
> 
> Please note this is intended as a shorter than normal release cycle
> given the limited scope and the importance of getting some of these
> fixes to those already trying 1.19.  If we need to extend due to lack
> of vote participation we will.
> 
> I am pleased to be calling this vote for the source release of Apache
> NiFi 1.19.1.
> 
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1218
> 
> The source being voted upon and the convenience binaries can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.19.1/
> 
> A helpful reminder on how the release candidate verification process works:
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> 
> The Git tag is nifi-1.19.1-RC2
> The Git commit ID is a7236ecc9123113ba5b9aaa3baab06354778116f
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=a7236ecc9123113ba5b9aaa3baab06354778116f
> 
> Checksums of nifi-1.19.1-source-release.zip:
> SHA256: 1172b133096c9d88b185413afc1eb6220d3f0542df6cdf82ceb7b01ae6fa15ed
> SHA512: 
> 3b571c9151bb755653f5e5ca3c275813134572c0fc28d8730a0dc5c1390df118b2be1f013f9acc0e394a959ff5dc853402f2c03d8f504010d6b835b43d786784
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
> 
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> 36 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12352626
> 
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.19.1
> 
> The vote will be open for 36 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> from source, and test. Then please vote:
> 
> [ ] +1 Release this package as nifi-1.19.1
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...

Re: [VOTE] Release Apache NiFi 1.19.0 (RC1)

[Nandor Soma Abonyi]

+1 (non-binding)

I’ve found two minor issues. I believe none of them is a blocker, but we should 
follow up on them. Marked them with ***.

Went through the release helper guide on:
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Java version: 1.8.0_332, vendor: Temurin
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"

Imported flows from NiFi registry for these issues and verified them:
- NIFI-10760 - Add Api key authentication option to 
ElasticSearchClientServiceImpl
- *** A validation has been removed, which prevented using Basic and Api 
Key properties together.
 If I set Username/Password and hide them by selecting Api Key 
Authorization Scheme, the client will still use those credentials. If I set Api 
Key, the client will add both credentials as a request header.
 Opened NIFI-10880 for further discussion.
- NIFI-10668 - Persist proxy password in remote process group
- NIFI-10656 - Log ignored event with info instead of warning in PutADLS
- NIFI-10650 - Fix demarcator is appended to the end of the FlowFile's content 
by ConsumeMQTT
- NIFI-10644 - Add Message Demarcator-style processing in PublishMQTT
- NIFI-10543 - Support broker failover in MQTT processors
- NIFI-10491 - PutAzureBlobStorage_v12 should have Conflict Resolution Strategy
- NIFI-10317 - NullPointerException if AMQP header value is null

*** Initially, I wanted to build NiFi in a docker container but experienced 
intermittent test failures. Most of the time, an 5 sec Test timeout caused 
issues in TestStandardFlowFileQueue.
  I don’t know why such a timeout was used, but I opened NIFI-10881 for 
further discussion.

Thanks for RM'ing Joe!
Regards,
Soma

> On Nov 23, 2022, at 4:58 PM, Joe Witt  wrote:
> 
> Hello,
> 
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.19.0.
> 
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1216
> 
> The source being voted upon and the convenience binaries can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.19.0/
> 
> A helpful reminder on how the release candidate verification process works:
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> 
> The Git tag is nifi-1.19.0-RC1
> The Git commit ID is ec87bf93add2f645d2ea426002e0c24db54614ff
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=ec87bf93add2f645d2ea426002e0c24db54614ff
> 
> Checksums of nifi-1.19.0-source-release.zip:
> SHA256: 909c4fce81b305af955540f83115474d139c132e886847df7b76e94efd3d4641
> SHA512:
> b3ba95984841140aa2a9a2ea471dd446d6fbd71dba320f723839e0938a7873f847e415a88b7c38e59907ad051c896949f0c7093c6d5e6b5db549de929ec32c6e
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
> 
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> 221 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12352150
> 
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.19.0
> 
> The vote will be open for at least 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> from source, and test. Then please vote:
> 
> [ ] +1 Release this package as nifi-1.19.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...

Re: [VOTE] Release Apache NiFi 1.18.0 (RC4)

[Nandor Soma Abonyi]

+1 (non-binding)

Went through the release helper guide on:
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Java version: 1.8.0_332, vendor: Temurin
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"

Also verified:
- NIFI-10251 - Add v5 protocol support for existing MQTT processors
- NIFI-10411 - Add record processing feature to PublishMQTT processor
- NIFI-10488 - Fix NullPointerException on updating empty ParameterContext 
property with NiFi Toolkit (tested multiple variations, create 
normal/sensitive, update normal/sensitive properties)
- NIFI-10152 - Storage client caching in Azure ADLS processors

Thanks for RM'ing Joe!
Regards,
Soma

> On Oct 3, 2022, at 10:44 PM, Joe Witt  wrote:
> 
> Hello,
> 
> I am pleased to be calling this vote for the source release of Apache
> NiFi 1.18.0.
> 
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1214
> 
> The source being voted upon and the convenience binaries can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.18.0/
> 
> A helpful reminder on how the release candidate verification process works:
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> 
> The Git tag is nifi-1.18.0-RC4
> The Git commit ID is 109e54cd585902a981d1b370b3dc4d1620be438c
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=109e54cd585902a981d1b370b3dc4d1620be438c
> 
> Checksums of nifi-1.18.0-source-release.zip:
> SHA256: 925cbb92c107d0fa3194a349d985cff4933a61b2555eff57b1b81433fe37c139
> SHA512: 
> f143215b1746342e7584f5ad65b546fcc378cd78aa17628fb605dfdbbaf11e897a0173dd67807fc90cb18c17124a4227d5fe07e7ed609d9ed1904503b757c604
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
> 
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> 184 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12352150
> 
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.18.0
> 
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> from source, and test. Then please vote:
> 
> [ ] +1 Release this package as nifi-1.18.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...

Re: [VOTE] Release Apache NiFi 1.18.0 (RC3)

[Nandor Soma Abonyi]

Hello,

Sorry for ruining the voting party…

-1 (non-binding)

The simplest GenerateFlowFile -> PutAzureDataLakeStorage flow throws an 
exception and results in failure. Verified that tests in 
ITPutAzureDataLakeStorage are also failing.
I think the reason is the Azure SDK upgrade.

Stack trace:
2022-10-02 12:14:47,389 ERROR [Timer-Driven Process Thread-9] 
o.a.n.p.a.s.PutAzureDataLakeStorage 
PutAzureDataLakeStorage[id=23aee885-b94b-3dc3-367c-5506568d5c16] Failed to 
create file on Azure Data Lake Storage
com.azure.storage.file.datalake.models.DataLakeStorageException: Status code 
412, "{"error":{"code":"ConditionNotMet","message":"The condition specified 
using HTTP conditional header(s) is not 
met.\nRequestId:bc39f465-e01f-001b-1b47-d6810400\nTime:2022-10-02T10:14:47.2730857Z"}}"
at 
java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)
at 
com.azure.core.implementation.http.rest.ResponseExceptionConstructorCache.invoke(ResponseExceptionConstructorCache.java:56)
at 
com.azure.core.implementation.http.rest.RestProxyBase.instantiateUnexpectedException(RestProxyBase.java:377)
at 
com.azure.core.implementation.http.rest.AsyncRestProxy.lambda$ensureExpectedStatus$1(AsyncRestProxy.java:117)
at 
reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:113)
at 
reactor.core.publisher.Operators$ScalarSubscription.request(Operators.java:2398)
at 
reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.request(FluxMapFuseable.java:171)
at 
reactor.core.publisher.Operators$MultiSubscriptionSubscriber.set(Operators.java:2194)
at 
reactor.core.publisher.Operators$MultiSubscriptionSubscriber.onSubscribe(Operators.java:2068)
at 
reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onSubscribe(FluxMapFuseable.java:96)
at reactor.core.publisher.MonoJust.subscribe(MonoJust.java:55)
at 
reactor.core.publisher.InternalMonoOperator.subscribe(InternalMonoOperator.java:64)
at 
reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:157)
at 
reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:129)
at 
reactor.core.publisher.FluxHide$SuppressFuseableSubscriber.onNext(FluxHide.java:137)
at 
reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:129)
at 
reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:129)
at 
reactor.core.publisher.FluxHide$SuppressFuseableSubscriber.onNext(FluxHide.java:137)
at 
reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:79)
at 
reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1816)
at 
reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:151)
at 
reactor.core.publisher.FluxDelaySubscription$DelaySubscriptionMainSubscriber.onNext(FluxDelaySubscription.java:189)
at 
reactor.core.publisher.SerializedSubscriber.onNext(SerializedSubscriber.java:99)
at 
reactor.core.publisher.SerializedSubscriber.onNext(SerializedSubscriber.java:99)
at 
reactor.core.publisher.FluxTimeout$TimeoutMainSubscriber.onNext(FluxTimeout.java:180)
at 
reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:129)
at 
reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:129)
at 
reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:129)
at 
reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1816)
at 
reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:151)
at 
reactor.core.publisher.SerializedSubscriber.onNext(SerializedSubscriber.java:99)
at 
reactor.core.publisher.FluxRetryWhen$RetryWhenMainSubscriber.onNext(FluxRetryWhen.java:174)
at 
reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:79)
at 
reactor.core.publisher.Operators$MonoInnerProducerBase.complete(Operators.java:2664)
at 
reactor.core.publisher.MonoSingle$SingleSubscriber.onComplete(MonoSingle.java:180)
at 
reactor.core.publisher.MonoFlatMapMany$FlatMapManyInner.onComplete(MonoFlatMapMany.java:260)
at 
reactor.core.publisher.FluxMap$MapSubscriber.onComplete(FluxMap.java:144)
at 
reactor.core.publisher.FluxDoFinally$DoFinallySubscriber.onComplete(FluxDoFinally.java:128)
at 
reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onComplete(FluxMapFuseable.java:152)
at 
reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1817)
at 
reactor.core.publisher.MonoCollect$CollectSubscriber.onComplete(MonoCollect.java:160)
at 
reactor.core.publisher.FluxHandle$HandleSubscriber.onComplet

Re: [VOTE] Release Apache NiFi 1.17.0 (RC2)

[Nandor Soma Abonyi]

+1 (non-binding)

Went through the release helper guide on:
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Java version: 1.8.0_332, vendor: Temurin
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"

Also verified:
- NIFI-9917 Fix tooltip of "delivery guarantee/best effort" in PublishKafka* 
and PublishKafkaRecord*
- NIFI-9951 Add proxy support to Azure ADLS and Blob v12 processors
- NIFI-10260 Improve the display name and description of Validate DTD property

Regards,
Soma

> On Jul 28, 2022, at 4:28 PM, Joe Witt  wrote:
> 
> Hello,
> 
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.17.0.
> 
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1210
> 
> The source being voted upon and the convenience binaries can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.17.0/
> 
> A helpful reminder on how the release candidate verification process works:
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> 
> The Git tag is nifi-1.17.0-RC2
> The Git commit ID is 8d256784d84cc28bf5642e1bf38dec3eba0c5f23
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=8d256784d84cc28bf5642e1bf38dec3eba0c5f23
> 
> Checksums of nifi-1.17.0-source-release.zip:
> SHA256: 8b9b2088ad966329248cfae7792f576f4f30fea4b4e50f055f84724dba4fe8a3
> SHA512:
> 2429348ad514ca7ab9df86aaa57207f1434044c6f7e947d0950ca9826b4f1aa51061617a17444c086eed19b1f26a5ebbe3b455cafed9d219727adf26ecb5f8d2
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
> 
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> 310 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12351438
> 
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.17.0
> 
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test. Then
> please vote:
> 
> [ ] +1 Release this package as nifi-1.17.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...

Re: Code review for NIFI-7865

[Nandor Soma Abonyi]

Hi Seda!

I’d like to help, but I only can in the evening. If nobody hops in until then, 
I’ll do it.

Best regards,
Soma

> On Nov 15, 2021, at 11:32 AM, Seda Dogan  wrote:
> 
> Hello together,
> 
> I have a pull request. https://github.com/apache/nifi/pull/5458 . I have 
> already an approve. I need one more.
> Can you help?
> 
> 
> Kind Regards
> Seda Dogan
> [ABAS ERP]
> abas Software GmbH | Gartenstraße 67 | 76135 Karlsruhe | Germany
> Phone: +49(0)721-96723-0 | Fax: +49(0)721-96723-100
> E-Mail: seda.do...@abas.de | Web: 
> https://abas-erp.com/de
> 
> [ABAS ERP 20 
> Release]
> 
> Managing Directors / Geschäftsführer: Richard Furby, Paul Smolinski
> Registered Office / Sitz der Gesellschaft: Karlsruhe
> Commercial Register / Handelsregister: HRB 734651 Amtsgericht Mannheim
> 
> [ISO 9001][BITMi Software Made in Germany]
> 
> Informationen zum Umgang mit Ihren personenbezogenen Daten nach den Art. 13 
> und 14 EU-DSGVO
> finden Sie unter https://abas-erp.com/de/datenschutz.
> Further information according to Art. 13 and 14 GDPR about processing your 
> personal data you can find
> here: https://abas-erp.com/en/privacy-copyright.