You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2022/04/09 10:39:00 UTC

[jira] [Updated] (FLINK-16043) Support non-BMP Unicode for JsonRowSerializationSchema

     [ https://issues.apache.org/jira/browse/FLINK-16043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-16043:
-----------------------------------
    Labels: auto-deprioritized-major auto-unassigned pull-request-available stale-minor  (was: auto-deprioritized-major auto-unassigned pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> Support non-BMP Unicode for JsonRowSerializationSchema
> ------------------------------------------------------
>
>                 Key: FLINK-16043
>                 URL: https://issues.apache.org/jira/browse/FLINK-16043
>             Project: Flink
>          Issue Type: Improvement
>          Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile)
>    Affects Versions: 1.10.0
>            Reporter: Benchao Li
>            Priority: Minor
>              Labels: auto-deprioritized-major, auto-unassigned, pull-request-available, stale-minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> This is a known issue for jackson: [https://github.com/FasterXML/jackson-core/issues/223]
> You can see more details: [https://github.com/FasterXML/jackson-core/blob/master/src/main/java/com/fasterxml/jackson/core/json/UTF8JsonGenerator.java#L2105]
>  
> And I also encountered this issue in my production environment. I've figured out a solution to solve this issue. Java's String.getBytes() can deal with UTF-8 encoding well. So we can do it like this:
> {{mapper.writeValueAsString(node).getBytes()}} instead of 
> {{mapper.writeValueAsBytes(node)}}
> cc [~jark] [~twalthr]



--
This message was sent by Atlassian Jira
(v8.20.1#820001)