You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ewen Cheslack-Postava (JIRA)" <ji...@apache.org> on 2016/11/14 17:14:58 UTC

[jira] [Commented] (KAFKA-4404) Add knowledge of sign to numeric schema types

    [ https://issues.apache.org/jira/browse/KAFKA-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664439#comment-15664439 ] 

Ewen Cheslack-Postava commented on KAFKA-4404:
----------------------------------------------

What is the motivation for this? Support for signed and unsigned types is spotty at best in serialization formats, see https://cwiki.apache.org/confluence/display/KAFKA/Copycat+Data+API for some of the survey done when initially working on the API (basically protobufs is the only format that has complete support). Being exhaustive in type support ends up being a burden for connector and converter developers as it requires more effort to support all the types, so I think it's important to make sure any additions to the set of supported types are well motivated.

> Add knowledge of sign to numeric schema types
> ---------------------------------------------
>
>                 Key: KAFKA-4404
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4404
>             Project: Kafka
>          Issue Type: Improvement
>          Components: KafkaConnect
>    Affects Versions: 0.10.0.1
>            Reporter: Andy Bryant
>            Assignee: Ewen Cheslack-Postava
>            Priority: Minor
>
> For KafkaConnect schemas there is currently no concept of whether a numeric field is signed or unsigned. 
> Add an additional `signed` attribute (like optional) or make it explicit that numeric types must be signed.
> You could encode this as a parameter on the schema but this would not be standard across all connectors.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)