flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Márton Balassi <balassi.mar...@gmail.com>
Subject The household of the Kafka connector
Date Mon, 22 Jun 2015 12:08:30 GMT

Due to the effort invested to the Kafka connector mainly by Robert and
Gabor Hermann we are going to ship a fairly nice solution for reading from
and writing to Kafka with 0.9.0. This is the most prominent streaming
connector currently, and rightfully so as pipeline level end-to-end exactly
once processing for streaming is dependent on it in this release.

To make it even more user-friendly and efficient I find the following tasks

1. Currently we ship two Kafka sources and for historic reason the
non-persistent one is called KafkaSource and the persistent one is
PersistentKafkaSource, the latter is also more difficult to find. Although
the former one is easier to read and a bit faster, let us enforce that
people use the fault-tolerant version by default. The behavior is already
documented both in javadoc and on the Flink website. Reported by Ufuk.

Proposed solution: Deprecate the non-persistent KafkaSource, may be move
the PersistentKafkaSource to org.apache.flink.streaming.kafka. (Currently
it is in its subpackage, persistent.) Eventually we could even rename the
current PersistentKafkaSource to KafkaSource.

2. The documentation of the streaming connectors is a bit hidden on the
website. These are not included in the connectors section [1], but are at
the very end of the streaming guide. [2]

Proposed solution: Move them to connectors and link it from the streaming

3. Collocate the KafkaSource and the KafkaSink with the corresponding
Brokers if possible for improved performance. There is a ticket for this.

4. Handling Broker failures on the KafkaSink side.

Currently instead of looking for a new Broker the sink throws an exception
and thus cancels the job if the Broker failes. Assuming that the job has
execution retries left and an available Broker to write to the job comes
back, finds the Broker and continues. Added a ticket for it just now.
[4] Reported
by Aljoscha.

[3] https://issues.apache.org/jira/browse/FLINK-1673
[4] https://issues.apache.org/jira/browse/FLINK-2256



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message