Github user HungUnicorn commented on a diff in the pull request:
https://github.com/apache/flink/pull/3036#discussion_r94943539
--- Diff:
flink-connectors/flink-connector-kafka-0.9/src/main/java/org/apache/flink/streaming/connectors/kafka/FlinkKafkaConsumer09.java
---
@@ -208,13
GitHub user HungUnicorn reopened a pull request:
https://github.com/apache/flink/pull/3036
[FLINK-5368] Throw exception if kafka topic doesn't exist
As a developer when reading data from many topics, I want Kafka consumer to
show something if any topic is not avai
Github user HungUnicorn closed the pull request at:
https://github.com/apache/flink/pull/3036
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user HungUnicorn commented on a diff in the pull request:
https://github.com/apache/flink/pull/3036#discussion_r93916373
--- Diff:
flink-connectors/flink-connector-kafka-0.9/src/main/java/org/apache/flink/streaming/connectors/kafka/FlinkKafkaConsumer09.java
---
@@ -208,13
GitHub user HungUnicorn opened a pull request:
https://github.com/apache/flink/pull/3036
[FLINK-5368] Throw exception if kafka topic doesn't exist
As a developer when reading data from many topics, I want Kafka consumer to
show something if any topic is not available.
Github user HungUnicorn commented on the issue:
https://github.com/apache/flink/pull/1962
Using the sniffing feature of transport client can achieve this.
The client will connect to all existing nodes and the connected list is
updated every 5 seconds. It can fit our case because
Github user HungUnicorn commented on a diff in the pull request:
https://github.com/apache/flink/pull/1040#discussion_r55013666
--- Diff:
flink-staging/flink-streaming/flink-streaming-connectors/flink-connector-elasticsearch/src/main/java/org/apache/flink/streaming/connectors
