You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Erik van Oosten (JIRA)" <ji...@apache.org> on 2017/06/15 08:29:00 UTC
[jira] [Updated] (FLINK-6928) Kafka sink: default topic should not
need to exist
[ https://issues.apache.org/jira/browse/FLINK-6928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erik van Oosten updated FLINK-6928:
-----------------------------------
Description:
When using a Kafka sink, the defaultTopic needs to exist even when it is never used. It would be nice if fetching partition information for the default topic would be delayed until the moment a topic is actually used.
Cause: {{FlinkKafkaProducerBase.open}} fetches partition information for the default topic.
was:
When using a Kafka source, the defaultTopic needs to exist even when it is never used. It would be nice if fetching partition information for the default topic would be delayed until the moment a topic is actually used.
Cause: {{FlinkKafkaProducerBase.open}} fetches partition information for the default topic.
> Kafka sink: default topic should not need to exist
> --------------------------------------------------
>
> Key: FLINK-6928
> URL: https://issues.apache.org/jira/browse/FLINK-6928
> Project: Flink
> Issue Type: Bug
> Components: Kafka Connector
> Affects Versions: 1.3.0, 1.2.1
> Reporter: Erik van Oosten
>
> When using a Kafka sink, the defaultTopic needs to exist even when it is never used. It would be nice if fetching partition information for the default topic would be delayed until the moment a topic is actually used.
> Cause: {{FlinkKafkaProducerBase.open}} fetches partition information for the default topic.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)