You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Umesh Chaudhary (JIRA)" <ji...@apache.org> on 2017/12/13 03:22:02 UTC

[jira] [Commented] (KAFKA-6342) Move workaround for JSON parsing of non-escaped strings

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

Umesh Chaudhary commented on KAFKA-6342:
----------------------------------------

[~ijuma] [~rsivaram] I will work on this. Just to confirm my understanding on this: 

[#4303|https://github.com/apache/kafka/pull/4303] adds a workaround to parse JSON by escaping backslash contained in SSL principals. We need to move this workaround so that it can only be applied for ACL JSON Parsing and keep the previous {{kafka.utils.Json#parseFull}} as it is. Please correct me if my understanding is not correct.

> 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
>             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)