[
https://issues.apache.org/jira/browse/FLINK-35427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871385#comment-17871385
]
huhuan commented on FLINK-35427:
--------------------------------
[~lzljs3620320] PTAL
> Support fail-on-unknown-field config in json format
> ---------------------------------------------------
>
> Key: FLINK-35427
> URL: https://issues.apache.org/jira/browse/FLINK-35427
> Project: Flink
> Issue Type: Improvement
> Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile)
> Reporter: huhuan
> Priority: Major
> Labels: pull-request-available
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> In many cases, the consumer and producer of message queues come from
> different teams, or even different companies.
> As message consumer, sometimes it is difficult to subscribe updates on
> message format, which may result in data loss.
> We want to ensure the message format strictly matches the schema, if some
> field is missing or new field is added, it is better to fail the application
> so that we can notice and fix it quickly.
> In this case, a fail-on-unknown-field config for JSON format could be very
> helpful, especially when works with fail-on-missing-field.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
