You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Colin McCabe (Jira)" <ji...@apache.org> on 2021/06/15 14:26:00 UTC

[jira] [Commented] (KAFKA-10898) Support snakeCaseName/camelCaseName JSON field name in JsonConverterGenerator

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

Colin McCabe commented on KAFKA-10898:
--------------------------------------

Hmm... Isn't it better just to standardize on one thing? Camel case seems fine for the message format JSON files.

> Support snakeCaseName/camelCaseName JSON field name in JsonConverterGenerator
> -----------------------------------------------------------------------------
>
>                 Key: KAFKA-10898
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10898
>             Project: Kafka
>          Issue Type: Improvement
>          Components: protocol
>            Reporter: dengziming
>            Assignee: dengziming
>            Priority: Minor
>
> I find many JSON-format command line params for example `kafka-reassign-partitions.sh --reassignment-json-file my.json` which we can use JsonConverter to read and write.
> However, currently, we use camelCaseName when converting protocol data to JSON, but most JSON-format command line params use snakeCaseName, so we should support snakeCaseName in JsonConverterGenerator.
> In the post-KIP-500 world, we will move all configs in zookeeper to kafka-raft, and the data in zookeeper is also stored as snakeCaseName JSON, so it's useful to support snakeCaseName in JsonConverterGenerator in advance.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)