[
https://issues.apache.org/jira/browse/KAFKA-7750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16724893#comment-16724893
]
Manjeet Duhan commented on KAFKA-7750:
--------------------------------------
conncector json we use it as design document that gets checked into our system,
also its helpful to make adhoc changes and comments, multi-line strings make it
easy to test it out. plain json makes it un-usable as connector config design
as un-usable artifact.
What's the confluent recommendation to manage and design the connector jsons as
they can be large. We thought HJSON looks better than yaml mainly managing
indentation.
> Hjson support in kafka connect
> ------------------------------
>
> Key: KAFKA-7750
> URL: https://issues.apache.org/jira/browse/KAFKA-7750
> Project: Kafka
> Issue Type: Improvement
> Reporter: Manjeet Duhan
> Priority: Major
> Attachments: image-2018-12-18-10-07-22-944.png
>
>
> I agree that json format is most accepted format among applications to
> communicate but this json is programme friendly , We needed something user
> friendly where we can pass comments comments as part of connector
> configuration.
> Features of Hjson :-
> # We are allowed to use comments
> # We are allowed to pass json as part of connector configuration key without
> escaping it which is very user friendly. (We have modified version of
> kafka-connect-elasticsearch where user can pass index mapping part of
> connector properties).
> Please find attached connector configuration in Json and Hjson. We are
> already running this in production. I have introduced HJSON filter on POST
> and PUT apis of kafka connect
> !image-2018-12-18-10-07-22-944.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
