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

Posted to jira@kafka.apache.org by "Jason Gustafson (Jira)" <ji...@apache.org> on 2020/05/06 19:41:00 UTC

[jira] [Assigned] (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:all-tabpanel ]

Jason Gustafson reassigned KAFKA-6342:
--------------------------------------

    Fix Version/s: 2.6.0
         Assignee: Viktor Somogyi-Vass  (was: Umesh Chaudhary)
       Resolution: Fixed

We found that the compatibility logic had not been used since 1.1, so we ultimately decided to remove it.

> 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: Viktor Somogyi-Vass
>            Priority: Major
>             Fix For: 2.6.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
(v8.3.4#803005)