You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Ewen Cheslack-Postava (JIRA)" <ji...@apache.org> on 2018/06/07 04:55:00 UTC

[jira] [Updated] (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:all-tabpanel ]

Ewen Cheslack-Postava updated KAFKA-6161:
-----------------------------------------
    Labels: needs-kip  (was: )

> 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)