greyp9 opened a new pull request #5613:
URL: https://github.com/apache/nifi/pull/5613


   #### Description of PR
   
   Add new NiFi NARs `nifi-kafka-3-0-processors` and `nifi-kafka-3-0-nar`.  
These are copies of the kafka-2-6 NARs as of git commit 
`b578f183cb593eae8a845d82f7fc28615e043ae9`, with minor changes to account for 
Kafka 3.0 method API updates.
   
   To manage the size of the nifi-assembly binary distributable, we may 
consider removing certain versions of nifi-kafka.  At present, the following 
kafka nars are included:
   - nifi-kafka-1-0-nar
   - nifi-kafka-2-0-nar
   - nifi-kafka-2-6-nar
   - nifi-kafka-3-0-nar (NEW)
   
   All nifi-kafka versions will continue to be built; this would just affect 
the content of the nifi-assembly binary.
   
   The `nifi-kafka-3-0-processors` references to Scala remain at version 2.13, 
which is unchanged from `nifi-kafka-2-6-processors`.
   
   Additional information about Kafka 3.0 may be found here:
   - https://kafka.apache.org/downloads
   
   Tested a single node NiFi instance and a three node NiFi cluster against a 
local Kafka 3.0.0 instance (single node) using topics with three partitions.  
GenerateFlowFile was at the head of the data flow, with two PublishKafka_3_0 / 
ConsumeKafka_3_0 pairs, and terminating with a PutFile.
   
   
   In order to streamline the review of the contribution we ask you
   to ensure the following steps have been taken:
   
   ### For all changes:
   - [x] Is there a JIRA ticket associated with this PR? Is it referenced 
        in the commit message?
   
   - [x] 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.
   
   - [x] Has your PR been rebased against the latest commit within the target 
branch (typically `main`)?
   
   - [x] 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:
   - [x] Have you ensured that the full suite of tests is executed via `mvn 
-Pcontrib-check clean install` at the root `nifi` folder?
   - [x] Have you written or updated unit tests to verify your changes?
   - [x] Have you verified that the full build is successful on JDK 8?
   - [x] Have you verified that the full build is successful on 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](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] 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 GitHub Actions CI for 
build issues and submit an update to your PR as soon as possible.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to