[
https://issues.apache.org/jira/browse/FLINK-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984528#comment-15984528
]
ASF GitHub Bot commented on FLINK-6288:
---------------------------------------
Github user fanyon commented on the issue:
https://github.com/apache/flink/pull/3766
The new API should in a new class, such as FlinkKafkaPartitioner. For the
older KafkaPartitioner implementation, it will be delegated by
FlinkKafkaAdpterPartitioner extends FlinkKafkaPartitioner, in which contains
defaultTopicId/partitions and KafkaPartitioner delegate, and map the new api to
the current one in terms. Of course, as it is now, default topic's partitions
will be used for the diffrent target topics in FlinkKafkaAdpterPartitioner.
> FlinkKafkaProducer's custom Partitioner is always invoked with number of
> partitions of default topic
> ----------------------------------------------------------------------------------------------------
>
> Key: FLINK-6288
> URL: https://issues.apache.org/jira/browse/FLINK-6288
> Project: Flink
> Issue Type: Improvement
> Components: Kafka Connector
> Reporter: Tzu-Li (Gordon) Tai
> Assignee: Fang Yong
>
> The {{FlinkKafkaProducerBase}} supports routing records to topics besides the
> default topic, but the custom {{Partitioner}} interface does not follow this
> semantic.
> The partitioner is always invoked the {{partition}} method with the number of
> partitions in the default topic, and not the number of partitions of the
> current {{targetTopic}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
