[
https://issues.apache.org/jira/browse/FLINK-23933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17419670#comment-17419670
]
Ingo Bürk commented on FLINK-23933:
-----------------------------------
{quote}This should already work
{quote}
That's not what I meant. Basically, given the example from the issue, I think
`a STRING` should just work without the need for extra format-specific options.
Just declaring the schema that way is enough information to deserialize
appropriately. That said, it probably should be one option to switch between a
strict and lenient mode (this behavior being lenient mode).
> flink-json formats support a option to parse nested json as a String
> --------------------------------------------------------------------
>
> Key: FLINK-23933
> URL: https://issues.apache.org/jira/browse/FLINK-23933
> Project: Flink
> Issue Type: Improvement
> Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile)
> Affects Versions: 1.13.2
> Reporter: Shengnan YU
> Priority: Major
>
> When use Flink SQL to read message with nested json, eg. \{"a":{"b":111,
> "c":"xxx"}, "d":12345}，The nested field must be specified ROW or MAP in the
> table schema.
> {code:sql}
> CREATE TABLE input(
> a ROW(`b`: BIGINT, `c` VARCHAR),
> d BIGINT
> )
> WITH (
> 'format' = 'json',
> // ...
> );
> {code}
> I'd like to create a option to allow we read the json-object type value as a
> String.
> {code:sql}
> CREATE TABLE input (
> a VARCHAR,
> d VARCHAR
> )
> WITH (
> 'format' = 'json',
> 'json.forceStringFields' = 'a,d'
> // ...
> );
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
