[
https://issues.apache.org/jira/browse/KAFKA-6342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300962#comment-16300962
]
ASF GitHub Bot commented on KAFKA-6342:
---------------------------------------
umesh9794 commented on issue #4321: KAFKA-6342 : Move workaround for JSON
parsing of non-escaped strings
URL: https://github.com/apache/kafka/pull/4321#issuecomment-353522531
@ijuma thanks for the suggestion, makes sense. I also need @rajinisivaram's
confirmation on `Json.parseBytes` in `Acl` class based on our above
observations.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Move workaround for JSON parsing of non-escaped strings
> -------------------------------------------------------
>
> Key: KAFKA-6342
> URL: https://issues.apache.org/jira/browse/KAFKA-6342
> Project: Kafka
> Issue Type: Task
> Components: core
> Reporter: Rajini Sivaram
> Assignee: Umesh Chaudhary
> Fix For: 1.1.0
>
>
> KAFKA-6319 added a workaround to parse invalid JSON persisted using older
> versions of Kafka because special characters were not escaped. The workaround
> is required in 1.0.1 to enable parsing invalid JSON from ACL configs in
> ZooKeeper. We can move the workaround out of kafka.utils.Json#parseFull for
> 1.1.0 so that it is applied only to ACLs.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
