You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Chia-Ping Tsai (JIRA)" <ji...@apache.org> on 2018/07/01 05:36:00 UTC
[jira] [Commented] (KAFKA-6161) Introduce new serdes interfaces
with empty configure() and close()
[ https://issues.apache.org/jira/browse/KAFKA-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16528980#comment-16528980 ]
Chia-Ping Tsai commented on KAFKA-6161:
---------------------------------------
I will take over this Jira tomorrow. [~evis] Feel free to stop me.:)
> 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)