You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2016/03/05 03:09:40 UTC
[jira] [Updated] (KAFKA-3336) Unify ser/de pair classes into one
serde class
[ https://issues.apache.org/jira/browse/KAFKA-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guozhang Wang updated KAFKA-3336:
---------------------------------
Description:
Right now users must provide two separate classes for serializers and deserializers, respectively. This means the current API functions have at least 2 * numberOfTypes parameters.
*Example (current, bad): "foo(..., longSerializer, longDeserializer)".*
Because the serde aspect of the API is already one of the biggest UX issues, we should unify the serde functionality into a single serde class, i.e. one class that provides both serialization and deserialization functionality. This will reduce the number of required serde parameters in the API by 50%.
*Example (suggested, better): "foo(..., longSerializerDeserializer)"*.
* Note: This parameter name is horrible and only used to highlight the difference to the "current" example above.
We also want to 1) add a pairing function for each operator that does not require serialization, and 2) provide default serdes for common data types.
was:
Right now users must provide two separate classes for serializers and deserializers, respectively. This means the current API functions have at least 2 * numberOfTypes parameters.
*Example (current, bad): "foo(..., longSerializer, longDeserializer)".*
Because the serde aspect of the API is already one of the biggest UX issues, we should unify the serde functionality into a single serde class, i.e. one class that provides both serialization and deserialization functionality. This will reduce the number of required serde parameters in the API by 50%.
*Example (suggested, better): "foo(..., longSerializerDeserializer)"*.
* Note: This parameter name is horrible and only used to highlight the difference to the "current" example above.
> Unify ser/de pair classes into one serde class
> ----------------------------------------------
>
> Key: KAFKA-3336
> URL: https://issues.apache.org/jira/browse/KAFKA-3336
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Guozhang Wang
> Priority: Blocker
> Fix For: 0.10.0.0
>
>
> Right now users must provide two separate classes for serializers and deserializers, respectively. This means the current API functions have at least 2 * numberOfTypes parameters.
> *Example (current, bad): "foo(..., longSerializer, longDeserializer)".*
> Because the serde aspect of the API is already one of the biggest UX issues, we should unify the serde functionality into a single serde class, i.e. one class that provides both serialization and deserialization functionality. This will reduce the number of required serde parameters in the API by 50%.
> *Example (suggested, better): "foo(..., longSerializerDeserializer)"*.
> * Note: This parameter name is horrible and only used to highlight the difference to the "current" example above.
> We also want to 1) add a pairing function for each operator that does not require serialization, and 2) provide default serdes for common data types.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)