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

2024-01-27 Thread Krisztina Zsihovszki
+1 (non-binding)

- Verified signatures and hashes
- Ran build using Maven 3.8.7 on macOS 13.5 with openjdk 11.0.18 2023-01-17
and Zulu17.42+19-CA (build 17.0.7+7-LTS)
- Contrib check, unit tests passed

Checked basic flows and verified the following tickets:

[NIFI-12331] - Introduce a PublishSlack processor
[NIFI-12386] - Add a FilterAttribute processor


Thanks for RM'ing, Pierre!
Regards,

Krisztina

On Sat, Jan 27, 2024 at 4:43 PM Márk Báthori  wrote:

> +1 non-binding
>
> Went through the verification guide, verified hashes and signatures, ran a
> full build on NiFi with contrib-check successfully.
>
> Environment:
> - MacOs 13.4 (22F66)
> - OpenJDK Runtime Environment Zulu11.62+17-CA (build 11.0.18+10-LTS)
> - Apache Maven 3.8.6
>
> Created and ran various simple flows.
>
> Tested the following tickets:
> NIFI-11992 - Add PutZendeskTicket Processor and ZendeskRecordSink
> NIFI-12520 - ExtractHL7Attributes processor ignores repeatable field values
>
> Thanks for RMing Pierre!
>
> Regards,
> Mark
>
> David Handermann  ezt írta (időpont: 2024.
> jan. 27., Szo, 5:37):
>
> > +1 binding
> >
> > - Verified signatures and hashes
> > - Ran build using Maven Wrapper 3.9.6
> > - Ran build on macOS 14.2.1 with Azul Zulu JDK 1.8.0-392 AArch64
> > - Ran build on macOS 14.2.1 with Azul Zulu JDK 17.0.9 AArch64
> > - Ran build on Ubuntu 22.04 with Azul Zulu JDK 1.8.0-345 x86_64
> > - Ran build on Ubuntu 22.04 with Azul Zulu JDK 17.0.7 x86_64
> > - Ran NiFi system tests on macOS 14.2.1 with Azul Zulu JDK 1.8.0-392
> > AArch64
> > - Ran NiFi system tests on Ubuntu 22.04 with Azul Zulu JDK 1.8.0-345
> x86_64
> >
> > In the process of running the system tests, I found a failure for
> > DefaultedDynamicClassPathModificationIT. This test is failing due to
> > an upgrade from commons-lang3 3.13.0 to 3.14.0, and the fact that the
> > test class is looking for a particular version.
> >
> > I created Jira issue NIFI-12680 [1] and submitted a pull request to
> > resolve the problem, following the same approach already implemented
> > on the main branch.
> >
> > Based on the fact that the system tests are not part of the standard
> > review, and the fact that the failure relates to the test code itself,
> > I do not see this as a blocking issue for releasing this version.
> >
> > Thanks Pierre!
> >
> > Regards,
> > David Handermann
> >
> > On Thu, Jan 25, 2024 at 12:53 PM Pierre Villard
> >  wrote:
> > >
> > > Team,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > > 1.25.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.25.0
> > >
> > > The build artifacts are available on the Apache Nexus Repository:
> > >
> > > https://repository.apache.org/content/repositories/orgapachenifi-1263
> > >
> > > Git Tag: nifi-1.25.0-RC1
> > > Git Commit ID: 6ecc398d3f92425447e43242af4992757e25b3c5
> > > GitHub Commit Link:
> > >
> >
> https://github.com/apache/nifi/commit/6ecc398d3f92425447e43242af4992757e25b3c5
> > >
> > > Checksums of nifi-1.25.0-source-release.zip
> > >
> > > SHA256:
> 6a14b35bf5beb4ae3fcf76df8d09676e61c6bc309a97dc6785eae84b7cbaef78
> > > SHA512:
> > >
> >
> 1ffb2586ce9591ce2c5aa39fdec43a89ffd29081a31d51dc95dd953cb7f94584d0a0171bb1ba7c9495f431aec3770d324dbabb319b01bb6fdce5a0a00426fffa
> > >
> > > 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: 103
> > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353860
> > >
> > > Release note highlights can be found on the project wiki:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.25.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.25.0
> > > [] +0 no opinion
> > > [] -1 Do not release this package because...
> >
>


Re: Apache NIFI: Query on logging.

2024-01-27 Thread Mark Payne
Kumar,

As Pierre noted LogAttribute can log the payload as well. However it’s worth 
nothing that it’s generally considered a bad practice to litter the flow with 
logging processors. Instead, you should take a look at NiFi’s Data Provenance 
[1] features.

Thanks
Mark

[1] https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#data_provenance

Sent from my iPhone

On Jan 27, 2024, at 10:16 AM, Pierre Villard  
wrote:

LogAttribute can log the flowfile's content. Set Log Payload to true.

HTH,
Pierre

Le sam. 27 janv. 2024 à 18:45, Kumar Kapil  a
écrit :

Hi to NIFI dev team,



I have below requirements where documentation or your assistance is
required in the logging. Currently LogMessage and LogAttribute process are
supported. But is it enough to log json object or request body and response
body. We need a processor which can log file-flow content, JSON documents
and other useful information.



*Requirement 1: *

  - Consume events from the MQTT.
  - Log the events in the log file.
  - Transform the event by using JOLT Transformation.
  - Log the transformed JSON document in the log file.
  - Invoke HTTP request and post it.
  - Log request body and response body with http status code in log
  file.



*Requirement 2: *

  - Exposed Rest API from NIFI
  - Log request body in the log file
  - Send it to Kafka.
  - Log the Kafka event in the log file.



Regards,



Kumar Kapil

Software Architect



checkpoint
systems.com


+(91) 8050050113

kumar.ka...@checkpt.com







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

2024-01-27 Thread Márk Báthori
+1 non-binding

Went through the verification guide, verified hashes and signatures, ran a
full build on NiFi with contrib-check successfully.

Environment:
- MacOs 13.4 (22F66)
- OpenJDK Runtime Environment Zulu11.62+17-CA (build 11.0.18+10-LTS)
- Apache Maven 3.8.6

Created and ran various simple flows.

Tested the following tickets:
NIFI-11992 - Add PutZendeskTicket Processor and ZendeskRecordSink
NIFI-12520 - ExtractHL7Attributes processor ignores repeatable field values

Thanks for RMing Pierre!

Regards,
Mark

David Handermann  ezt írta (időpont: 2024.
jan. 27., Szo, 5:37):

> +1 binding
>
> - Verified signatures and hashes
> - Ran build using Maven Wrapper 3.9.6
> - Ran build on macOS 14.2.1 with Azul Zulu JDK 1.8.0-392 AArch64
> - Ran build on macOS 14.2.1 with Azul Zulu JDK 17.0.9 AArch64
> - Ran build on Ubuntu 22.04 with Azul Zulu JDK 1.8.0-345 x86_64
> - Ran build on Ubuntu 22.04 with Azul Zulu JDK 17.0.7 x86_64
> - Ran NiFi system tests on macOS 14.2.1 with Azul Zulu JDK 1.8.0-392
> AArch64
> - Ran NiFi system tests on Ubuntu 22.04 with Azul Zulu JDK 1.8.0-345 x86_64
>
> In the process of running the system tests, I found a failure for
> DefaultedDynamicClassPathModificationIT. This test is failing due to
> an upgrade from commons-lang3 3.13.0 to 3.14.0, and the fact that the
> test class is looking for a particular version.
>
> I created Jira issue NIFI-12680 [1] and submitted a pull request to
> resolve the problem, following the same approach already implemented
> on the main branch.
>
> Based on the fact that the system tests are not part of the standard
> review, and the fact that the failure relates to the test code itself,
> I do not see this as a blocking issue for releasing this version.
>
> Thanks Pierre!
>
> Regards,
> David Handermann
>
> On Thu, Jan 25, 2024 at 12:53 PM Pierre Villard
>  wrote:
> >
> > Team,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > 1.25.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.25.0
> >
> > The build artifacts are available on the Apache Nexus Repository:
> >
> > https://repository.apache.org/content/repositories/orgapachenifi-1263
> >
> > Git Tag: nifi-1.25.0-RC1
> > Git Commit ID: 6ecc398d3f92425447e43242af4992757e25b3c5
> > GitHub Commit Link:
> >
> https://github.com/apache/nifi/commit/6ecc398d3f92425447e43242af4992757e25b3c5
> >
> > Checksums of nifi-1.25.0-source-release.zip
> >
> > SHA256: 6a14b35bf5beb4ae3fcf76df8d09676e61c6bc309a97dc6785eae84b7cbaef78
> > SHA512:
> >
> 1ffb2586ce9591ce2c5aa39fdec43a89ffd29081a31d51dc95dd953cb7f94584d0a0171bb1ba7c9495f431aec3770d324dbabb319b01bb6fdce5a0a00426fffa
> >
> > 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: 103
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353860
> >
> > Release note highlights can be found on the project wiki:
> >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.25.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.25.0
> > [] +0 no opinion
> > [] -1 Do not release this package because...
>


Re: Apache NIFI: Query on logging.

2024-01-27 Thread Pierre Villard
LogAttribute can log the flowfile's content. Set Log Payload to true.

HTH,
Pierre

Le sam. 27 janv. 2024 à 18:45, Kumar Kapil  a
écrit :

> Hi to NIFI dev team,
>
>
>
> I have below requirements where documentation or your assistance is
> required in the logging. Currently LogMessage and LogAttribute process are
> supported. But is it enough to log json object or request body and response
> body. We need a processor which can log file-flow content, JSON documents
> and other useful information.
>
>
>
> *Requirement 1: *
>
>- Consume events from the MQTT.
>- Log the events in the log file.
>- Transform the event by using JOLT Transformation.
>- Log the transformed JSON document in the log file.
>- Invoke HTTP request and post it.
>- Log request body and response body with http status code in log
>file.
>
>
>
> *Requirement 2: *
>
>- Exposed Rest API from NIFI
>- Log request body in the log file
>- Send it to Kafka.
>- Log the Kafka event in the log file.
>
>
>
> Regards,
>
>
>
> Kumar Kapil
>
> Software Architect
>
>
>
> checkpoint
> systems.com
> 
>
> +(91) 8050050113
>
> kumar.ka...@checkpt.com
>
>
>
>
>


Apache NIFI: Query on logging.

2024-01-27 Thread Kumar Kapil
Hi to NIFI dev team,

I have below requirements where documentation or your assistance is required in 
the logging. Currently LogMessage and LogAttribute process are supported. But 
is it enough to log json object or request body and response body. We need a 
processor which can log file-flow content, JSON documents and other useful 
information.

Requirement 1:

  *   Consume events from the MQTT.
  *   Log the events in the log file.
  *   Transform the event by using JOLT Transformation.
  *   Log the transformed JSON document in the log file.
  *   Invoke HTTP request and post it.
  *   Log request body and response body with http status code in log file.

Requirement 2:

  *   Exposed Rest API from NIFI
  *   Log request body in the log file
  *   Send it to Kafka.
  *   Log the Kafka event in the log file.

Regards,

[cid:image001.png@01DA515C.145B9BC0]
Kumar Kapil
Software Architect

checkpoint
systems.com
[cid:image002.png@01DA515C.145B9BC0]+(91) 8050050113
[cid:image003.png@01DA515C.145B9BC0]kumar.ka...@checkpt.com




Re: [VOTE] Release Apache NiFi 2.0.0-M2 (RC4)

2024-01-27 Thread Márk Báthori
+1 non-binding

Went through the verification guide, verified hashes and signatures, ran a
full build on NiFi with contrib-check successfully.

Environment:
- MacOs 13.4 (22F66)
- OpenJDK Runtime Environment Zulu21.28+85-CA (build 21+35)
- Apache Maven 3.8.6

Created and ran various simple flows.

Tested the following tickets:

   - NIFI-11992 - Add PutZendeskTicket Processor and ZendeskRecordSink
   - NIFI-12334 - Implement GCS option for FileResourceService
   - NIFI-12520 - ExtractHL7Attributes processor ignores repeatable field
   values
   - NIFI-12528 - Funnels bug


Thanks for RMing David!

Regards,
Mark

Matt Burgess  ezt írta (időpont: 2024. jan. 27., Szo,
5:15):

> +1 (binding)
>
> Ran full build
>
> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: /Users/mburgess/.sdkman/candidates/maven/current
> Java version: 21, vendor: Oracle Corporation
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.2.1", arch: "aarch64", family: "mac"
>
> Verified various flows. Thanks for RM'ing David!
>
> -Matt
>
> On Thu, Jan 25, 2024 at 9:30 PM David Handermann <
> exceptionfact...@apache.org> wrote:
>
> > Team,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi 2.0.0-M2.
> >
> > 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 and the convenience binaries are available
> > on the Apache Distribution Repository:
> >
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M2
> >
> > The build artifacts are available on the Apache Nexus Repository:
> >
> > https://repository.apache.org/content/repositories/orgapachenifi-1264
> >
> > Git Tag: nifi-2.0.0-M2-RC4
> > Git Commit ID: 640b7bdfbbb8842f057a9bf49dc2b9b5d092abda
> > GitHub Commit Link:
> >
> >
> https://github.com/apache/nifi/commit/640b7bdfbbb8842f057a9bf49dc2b9b5d092abda
> >
> > Checksums of nifi-2.0.0-M2-source-release.zip
> >
> > SHA256: 1946eceb3ae4f541545e93ddc6dd2cbe2a3302a6a46e6c584f3ffc1c1bd1e18b
> > SHA512:
> >
> e8e67e1e67359553479c0721a1c49ae6706cc6882eadf92e1f5ccc2619637ab87119a06221980d4c34d99b7b6d9a2138c77440b407074090e727b5d4447ab799
> >
> > 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 for this version: 214
> >
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353861
> >
> > Release note highlights can be found on the project wiki:
> >
> >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M2
> >
> > 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-2.0.0-M2
> > [] +0 no opinion
> > [] -1 Do not release this package because...
> >
>