[
https://issues.apache.org/jira/browse/KAFKA-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16504243#comment-16504243
]
Ewen Cheslack-Postava commented on KAFKA-6161:
----------------------------------------------
I think it is now a compatible change to just provide default impls, but we
should have some documentation that this is true. If it is the case, we can
have a very minimal KIP process and just add the default impls, as long as the
KIP discussion also agrees on the correct default implementations (the
compatibility isn't the only issue – we also need to agree on a valid default
implementation).
Note that this is a bit different than the original request for an alternative
set of interfaces that provide these by default. Given we can use default impls
now, we'd probably also want to revise the description of this JIRA.
> Introduce new serdes interfaces with empty configure() and close()
> ------------------------------------------------------------------
>
> Key: KAFKA-6161
> URL: https://issues.apache.org/jira/browse/KAFKA-6161
> Project: Kafka
> Issue Type: Improvement
> Components: clients, streams
> Reporter: Evgeny Veretennikov
> Assignee: Evgeny Veretennikov
> Priority: Major
> Labels: needs-kip
>
> {{Serializer}}, {{Deserializer}} and {{Serde}} interfaces have methods
> {{configure()}} and {{close()}}. Pretty often one want to leave these methods
> empty. For example, a lot of serializers inside
> {{org.apache.kafka.common.serialization}} package have these methods empty:
> {code}
> @Override
> public void configure(Map<String, ?> configs, boolean isKey) {
> // nothing to do
> }
> @Override
> public void close() {
> // nothing to do
> }
> {code}
> To avoid such boilerplate, we may create new interfaces (like
> {{UnconfiguredSerializer}}), in which we will define these methods empty.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
