[
https://issues.apache.org/jira/browse/NIFI-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825363#comment-16825363
]
Bryan Bende commented on NIFI-3108:
-----------------------------------
Was thinking about this a little more with the relationship to NIFI-4133...
should we maybe make the current "Partitioner Class" property become
"Partitioner Strategy" (just change display name)?
The values would be "DefaultPartitioner" (existing), "RoundRobin" (existing),
"Static" (new), "Custom" (new)".
If "Static" is chosen, then it requires also specifying the "Partition"
property which is where the static value will come from.
If "Custom" is specified, then it will require specifying two additional
properties of "Custom Partitioner Class" and "Custom Partitioner JARs".
The advantage is that this approach lets us continue to use Allowable Values
drop down for the strategy and the existing default and round robin options,
and also makes it very clear when to use static or custom.
> PublishKafka Should Support Custom Partitioners
> -----------------------------------------------
>
> Key: NIFI-3108
> URL: https://issues.apache.org/jira/browse/NIFI-3108
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.0.0, 1.1.0
> Reporter: Bryan Bende
> Assignee: Koji Kawamura
> Priority: Minor
>
> Currently PublishKafka/PublishKafka_0_10 have a property for choosing the
> partitioner which equates to setting the 'partitioner.class' property on the
> Kafka client, but the property on the processor only allows selecting from
> "Default Partitioner" and "Round-Robin" partitioner which are provided by the
> Kafka client.
> If someone wants to implement their own partitioner, there currently isn't an
> easy way to add it to NiFi's classpath, and there is no way to specify it in
> the processor.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
