[
https://issues.apache.org/jira/browse/FLINK-20263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-20263:
-----------------------------------
Labels: auto-deprioritized-major auto-unassigned (was: auto-unassigned
stale-major)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 ago and has not received any updates so
it is being deprioritized. If this ticket is actually Major, please raise the
priority and ask a committer to assign you the issue or revive the public
discussion.
> Improve exception when metadata name mismatch
> ---------------------------------------------
>
> Key: FLINK-20263
> URL: https://issues.apache.org/jira/browse/FLINK-20263
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / API
> Affects Versions: 1.12.0
> Reporter: Dawid Wysakowicz
> Priority: Minor
> Labels: auto-deprioritized-major, auto-unassigned
>
> I'd suggest to slightly improve the exception message when there is a
> mismatch in the field name. It would be nice to provide with an example of a
> valid syntax.
> I used:
> {code}
> tstmp TIMESTAMP(3) METADATA,
> {code}
> Right now we get:
> {code}
> org.apache.flink.table.api.ValidationException: Invalid metadata key 'tstmp'
> in column 'tstmp' of table
> 'default_catalog.default_database.pageviews_per_region'. The DynamicTableSink
> class 'org.apache.flink.streaming.connectors.kafka.table.KafkaDynamicSink'
> supports the following metadata keys for writing:
> headers
> timestamp
> {code}
> would be nice to have something like:
> {code}
> org.apache.flink.table.api.ValidationException: Invalid metadata key 'tstmp'
> in column 'tstmp' of table
> 'default_catalog.default_database.pageviews_per_region'. The DynamicTableSink
> class 'org.apache.flink.streaming.connectors.kafka.table.KafkaDynamicSink'
> supports the following metadata keys for writing:
> headers
> timestamp
> Example:
> tstmp TIMESTAMP(3) METADATA FROM 'headers' -- I think it would be fine to
> simply pick up the first key, I understand it would be hard to derive the
> desired property
> {code}
> This would let users easier figure out the error in the syntax. I might've
> copied the example from somewhere, because of being lazy and I might not be
> aware of the other syntax. It would be hard for me to figure out what is the
> problem from the original exception.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
