[ 
https://issues.apache.org/jira/browse/FLINK-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982630#comment-15982630
 ] 

ASF GitHub Bot commented on FLINK-6288:
---------------------------------------

Github user gyfora commented on the issue:

    https://github.com/apache/flink/pull/3766
  
    Hi,
    Thanks for the PR!
    
    The first problem I noticed with this approach is that it will not work if 
users want to partition dynamically created topics (my use case actually). 
    
    We should have a default partitioner that could be applied to the unmatched 
topics and would always pass the correct partition number.


> 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)

Reply via email to