[
https://issues.apache.org/jira/browse/FLINK-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986298#comment-15986298
]
ASF GitHub Bot commented on FLINK-6288:
---------------------------------------
Github user fanyon commented on the issue:
https://github.com/apache/flink/pull/3766
@tzulitai Thank you for your reply. For 2, I think a new issue may be
created later.
For 1, it is really a problem for which will block the running job. There
may be two ways:
1. Depend on the timeout mechanism of kafka. When fetching partition meta
from kafka, some timeout configurations should be setted.
2. Using Future to get the partiton meta of kafka, and user can set the
timeout with configuration.
For the 1th way, problem may still exist for network and other reasons, so
I'm apt to use the 2ed way.
cc @gyfora
> 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)
