NIFI-8021: Provide the ability to pin partitions to particular hosts … #4672
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pvillard31
requested changes
Nov 18, 2020
| <h2>Consumer Partition Assignment</h2> | ||
| <p> | ||
| By default, this processor will subscribe to one or more Kafka topics in such a way that the topics to consume from are randomly | ||
| assigned to to the nodes in the NiFi cluster. Consider a scenario where a single Kafka topic has 8 partitions and the consuming |
There was a problem hiding this comment.
Suggested change
| assigned to to the nodes in the NiFi cluster. Consider a scenario where a single Kafka topic has 8 partitions and the consuming | |
| assigned to the nodes in the NiFi cluster. Consider a scenario where a single Kafka topic has 8 partitions and the consuming |
| </p> | ||
|
|
||
| <p> | ||
| In order to use a static mapping of Kafka partitions, the "Topic Name Format" must be set to "names" rather than "pattern." |
There was a problem hiding this comment.
Suggested change
| In order to use a static mapping of Kafka partitions, the "Topic Name Format" must be set to "names" rather than "pattern." | |
| In order to use a static mapping of Kafka partitions, the "Topic Name Format" must be set to "names" rather than "pattern". |
| <h2>Consumer Partition Assignment</h2> | ||
| <p> | ||
| By default, this processor will subscribe to one or more Kafka topics in such a way that the topics to consume from are randomly | ||
| assigned to to the nodes in the NiFi cluster. Consider a scenario where a single Kafka topic has 8 partitions and the consuming |
There was a problem hiding this comment.
Suggested change
| assigned to to the nodes in the NiFi cluster. Consider a scenario where a single Kafka topic has 8 partitions and the consuming | |
| assigned to the nodes in the NiFi cluster. Consider a scenario where a single Kafka topic has 8 partitions and the consuming |
| </p> | ||
|
|
||
| <p> | ||
| In order to use a static mapping of Kafka partitions, the "Topic Name Format" must be set to "names" rather than "pattern." |
There was a problem hiding this comment.
Suggested change
| In order to use a static mapping of Kafka partitions, the "Topic Name Format" must be set to "names" rather than "pattern." | |
| In order to use a static mapping of Kafka partitions, the "Topic Name Format" must be set to "names" rather than "pattern". |
| <h2>Consumer Partition Assignment</h2> | ||
| <p> | ||
| By default, this processor will subscribe to one or more Kafka topics in such a way that the topics to consume from are randomly | ||
| assigned to to the nodes in the NiFi cluster. Consider a scenario where a single Kafka topic has 8 partitions and the consuming |
There was a problem hiding this comment.
Suggested change
| assigned to to the nodes in the NiFi cluster. Consider a scenario where a single Kafka topic has 8 partitions and the consuming | |
| assigned to the nodes in the NiFi cluster. Consider a scenario where a single Kafka topic has 8 partitions and the consuming |
| </p> | ||
|
|
||
| <p> | ||
| In order to use a static mapping of Kafka partitions, the "Topic Name Format" must be set to "names" rather than "pattern." |
There was a problem hiding this comment.
Suggested change
| In order to use a static mapping of Kafka partitions, the "Topic Name Format" must be set to "names" rather than "pattern." | |
| In order to use a static mapping of Kafka partitions, the "Topic Name Format" must be set to "names" rather than "pattern". |
| <h2>Consumer Partition Assignment</h2> | ||
| <p> | ||
| By default, this processor will subscribe to one or more Kafka topics in such a way that the topics to consume from are randomly | ||
| assigned to to the nodes in the NiFi cluster. Consider a scenario where a single Kafka topic has 8 partitions and the consuming |
There was a problem hiding this comment.
Suggested change
| assigned to to the nodes in the NiFi cluster. Consider a scenario where a single Kafka topic has 8 partitions and the consuming | |
| assigned to the nodes in the NiFi cluster. Consider a scenario where a single Kafka topic has 8 partitions and the consuming |
| </p> | ||
|
|
||
| <p> | ||
| In order to use a static mapping of Kafka partitions, the "Topic Name Format" must be set to "names" rather than "pattern." |
There was a problem hiding this comment.
Suggested change
| In order to use a static mapping of Kafka partitions, the "Topic Name Format" must be set to "names" rather than "pattern." | |
| In order to use a static mapping of Kafka partitions, the "Topic Name Format" must be set to "names" rather than "pattern". |
…when using ConsumeKafka processors
pvillard31
approved these changes
Nov 18, 2020
driesva
pushed a commit
to driesva/nifi
that referenced
this pull request
Mar 19, 2021
…when using ConsumeKafka processors Signed-off-by: Pierre Villard <pierre.villard.fr@gmail.com> This closes apache#4672.
krisztina-zsihovszki
pushed a commit
to krisztina-zsihovszki/nifi
that referenced
this pull request
Jun 28, 2022
…when using ConsumeKafka processors Signed-off-by: Pierre Villard <pierre.villard.fr@gmail.com> This closes apache#4672.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…when using ConsumeKafka processors
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
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
main)?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
squashor use--forcewhen pushing to allow for clean monitoring of changes.For code changes:
mvn -Pcontrib-check clean installat the rootnififolder?LICENSEfile, including the mainLICENSEfile undernifi-assembly?NOTICEfile, including the mainNOTICEfile found undernifi-assembly?.displayNamein addition to .name (programmatic access) for each of the new properties?For documentation related changes:
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.