Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Thu, 9 Jun 2016 12:30:21 +0000 (UTC)
From: "Robert Metzger (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.12977013.1465419698000.39070.1465475421360@Atlassian.JIRA>
In-Reply-To: <JIRA.12977013.1465419698000@Atlassian.JIRA>
References: <JIRA.12977013.1465419698000@Atlassian.JIRA> <JIRA.12977013.1465419698526@arcas>
Subject: [jira] [Commented] (FLINK-4035) Bump Kafka producer in Kafka sink
 to Kafka 0.10.0.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 09 Jun 2016 12:30:23 -0000


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

Robert Metzger commented on FLINK-4035:
---------------------------------------

I haven't looked into the Kafka 0.10 changes in detail.

If the API didn't change between 9 and 10, users can probably manually force the Kafka 0.9 connector to use the 0.10 code (by putting the kafka 0.10 client into their pom).

> Bump Kafka producer in Kafka sink to Kafka 0.10.0.0
> ---------------------------------------------------
>
>                 Key: FLINK-4035
>                 URL: https://issues.apache.org/jira/browse/FLINK-4035
>             Project: Flink
>          Issue Type: Bug
>          Components: Kafka Connector
>    Affects Versions: 1.0.3
>            Reporter: Elias Levy
>            Priority: Minor
>
> Kafka 0.10.0.0 introduced protocol changes related to the producer.  Published messages now include timestamps and compressed messages now include relative offsets.  As it is now, brokers must decompress publisher compressed messages, assign offset to them, and recompress them, which is wasteful and makes it less likely that compression will be used at all.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)