[
https://issues.apache.org/jira/browse/FLINK-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009993#comment-16009993
]
ASF GitHub Bot commented on FLINK-6288:
---------------------------------------
Github user zjureel commented on the issue:
https://github.com/apache/flink/pull/3766
@tzulitai Thank you for your replay.
For 1, the `ExecutorService` is used to control timeout of fetching kafka
partitions. When fetch kafka partitions, a `Future` will be created and
executed in `ExecutorService`, which will wait for some mills and throw
exception for timeout.
For 2, I had deprecated constructors of 08 / 09/ 010 whose parameter is
`KafkaPartitioner` and add the same constructors with parameter
`FlinkKafkaPartitioner`.
I find the codes in master of apache/flink were modified relative large
some days ago, and I try rebase these modification soon. I think you can review
these issues after that, thank you.
> 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)
