[
https://issues.apache.org/jira/browse/KAFKA-6923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16545156#comment-16545156
]
Viktor Somogyi commented on KAFKA-6923:
---------------------------------------
[~chia7712] thanks for the idea. Would you please also add it to the KIP
discussion thread to see what the community is thinking about this? (this is
the KIP:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=87298242 ).
Personally I'd prefer not to deprecate the Serializer class. I think all of the
serializer/deserializer implementations in the project (Short, Int, String
Byte, etc.) uses the 2 parameter method and I think it would be a good practice
to leave the telescopic methods given that Java really doesn't have any other
ways to represent optional parameters which the "headers" would be.
> 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)
