[
https://issues.apache.org/jira/browse/KAFKA-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16504252#comment-16504252
]
Ewen Cheslack-Postava commented on KAFKA-6161:
----------------------------------------------
lol, thanks for the offer [~mjsax], that was more of an offer that if someone
wants to move this forward they could update relevant parts, sort out any KIP
necessary, and file PR. I added `needs-kip` annotation, which I clearly missed
in an earlier comment when I mentioned it needs a KIP to make compatibility
clear, though we might be able to skip that as of JDK8 support.
> 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)
