You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Benchao Li (Jira)" <ji...@apache.org> on 2020/07/13 15:20:00 UTC
[jira] [Commented] (FLINK-18002) Support forcing varchar type in
Json format
[ https://issues.apache.org/jira/browse/FLINK-18002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17156781#comment-17156781 ]
Benchao Li commented on FLINK-18002:
------------------------------------
Fixed via 3865f7b23c656c74b85b0eb5dd8b73a0f5f88b03 (1.12.0)
> Support forcing varchar type in Json format
> -------------------------------------------
>
> Key: FLINK-18002
> URL: https://issues.apache.org/jira/browse/FLINK-18002
> Project: Flink
> Issue Type: Improvement
> Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile)
> Reporter: Benchao Li
> Assignee: Benchao Li
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.0
>
>
> Currently in json format, if the field type is varchar, we will call `JsonNode.asText()` which we always assumes the JsonNode is a TextNode.
> However, in many cases, we want to force it as varchar for other types, etc ObjectNode. We should use `JsonNode.toString()` for other JsonNode instead of `JsonNode.asText()`.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)