[ https://issues.apache.org/jira/browse/KAFKA-6923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16546174#comment-16546174 ]
Chia-Ping Tsai commented on KAFKA-6923: --------------------------------------- the [link|http://mail-archives.apache.org/mod_mbox/kafka-dev/201501.mbox/%3CCAOeJiJh6Vkkca85bWYgkeOZ8rC6%2BKDh7zzq8vMKECL_7PNExTA%40mail.gmail.com%3E] of discussion thread in the KIP-336 seems be incorrect. It brings me to a dead thread. The correct one should be [here|https://lists.apache.org/thread.html/21155b13ef88bb04ae084d5c62a72fdecf8851ebf9a7fa2da0215d96@%3Cdev.kafka.apache.org%3E] > Consolidate ExtendedSerializer/Serializer and > ExtendedDeserializer/Deserializer > ------------------------------------------------------------------------------- > > Key: KAFKA-6923 > URL: https://issues.apache.org/jira/browse/KAFKA-6923 > Project: Kafka > Issue Type: Improvement > Components: clients > Reporter: Ismael Juma > Assignee: Viktor Somogyi > Priority: Major > Labels: needs-kip > Fix For: 2.1.0 > > > The Javadoc of ExtendedDeserializer states: > {code} > * Prefer {@link Deserializer} if access to the headers is not required. Once > Kafka drops support for Java 7, the > * {@code deserialize()} method introduced by this interface will be added to > Deserializer with a default implementation > * so that backwards compatibility is maintained. This interface may be > deprecated once that happens. > {code} > Since we have dropped Java 7 support, we should figure out how to do this. > There are compatibility implications, so a KIP is needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)