You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Tzu-Li (Gordon) Tai (JIRA)" <ji...@apache.org> on 2017/07/19 06:21:00 UTC
[jira] [Updated] (FLINK-7224) Incorrect Javadoc description in all
Kafka consumer versions
[ https://issues.apache.org/jira/browse/FLINK-7224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tzu-Li (Gordon) Tai updated FLINK-7224:
---------------------------------------
Description:
Currently, all Kafka consumer version still have this in the Javadoc:
{code}
The implementation currently accesses partition metadata when the consumer
is constructed. That means that the client that submits the program needs to be able to
reach the Kafka brokers or ZooKeeper.
{code}
This is also the case for the documentation:
{code}
The current FlinkKafkaConsumer implementation will establish a connection from the client (when calling the constructor) for querying the list of topics and partitions.
For this to work, the consumer needs to be able to access the consumers from the machine submitting the job to the Flink cluster. If you experience any issues with the Kafka consumer on the client side, the client log might contain information about failed requests, etc.
{code}
These statements are no longer true since starting from Flink 1.3. partition metadata happens only in {{open()}}.
was:
Currently, all Kafka consumer version still have this in the Javadoc:
{code}
The implementation currently accesses partition metadata when the consumer
is constructed. That means that the client that submits the program needs to be able to
reach the Kafka brokers or ZooKeeper.
{code}
This is also the case for the documentation:
{code}
The current FlinkKafkaConsumer implementation will establish a connection from the client (when calling the constructor) for querying the list of topics and partitions.
For this to work, the consumer needs to be able to access the consumers from the machine submitting the job to the Flink cluster. If you experience any issues with the Kafka consumer on the client side, the client log might contain information about failed requests, etc.
{code}
These statements are no longer true since Flink 1.3. partition metadata happens only in {{open()}}.
> Incorrect Javadoc description in all Kafka consumer versions
> ------------------------------------------------------------
>
> Key: FLINK-7224
> URL: https://issues.apache.org/jira/browse/FLINK-7224
> Project: Flink
> Issue Type: Improvement
> Components: Kafka Connector
> Affects Versions: 1.3.1, 1.4.0
> Reporter: Tzu-Li (Gordon) Tai
> Assignee: Tzu-Li (Gordon) Tai
>
> Currently, all Kafka consumer version still have this in the Javadoc:
> {code}
> The implementation currently accesses partition metadata when the consumer
> is constructed. That means that the client that submits the program needs to be able to
> reach the Kafka brokers or ZooKeeper.
> {code}
> This is also the case for the documentation:
> {code}
> The current FlinkKafkaConsumer implementation will establish a connection from the client (when calling the constructor) for querying the list of topics and partitions.
> For this to work, the consumer needs to be able to access the consumers from the machine submitting the job to the Flink cluster. If you experience any issues with the Kafka consumer on the client side, the client log might contain information about failed requests, etc.
> {code}
> These statements are no longer true since starting from Flink 1.3. partition metadata happens only in {{open()}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)