[
https://issues.apache.org/jira/browse/FLINK-15232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jingsong Lee updated FLINK-15232:
---------------------------------
Description:
Currently, all the required properties should exist and match, otherwise,
{{NoMatchingTableFactoryException}} will be thrown.
User have no idea to know what is wrong.
We can pick a best candidate to print where is wrong, print requiredContext
and supportedProperties in different formats.
In this way, users can know which property in requiredContext is lack, and
which property is not allow in supportedProperties.
was:
Currently, all the required properties should exist and match, otherwise,
{{NoMatchingTableFactoryException}} will be thrown.
We can pick a best candidate to print where is wrong, print requiredContext
and supportedProperties in different formats.
In this way, users can know which property in requiredContext is lack, and
which property is not allow in supportedProperties.
> Print match candidates to improve NoMatchingTableFactoryException
> -----------------------------------------------------------------
>
> Key: FLINK-15232
> URL: https://issues.apache.org/jira/browse/FLINK-15232
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / API
> Reporter: Jingsong Lee
> Assignee: Jingsong Lee
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, all the required properties should exist and match, otherwise,
> {{NoMatchingTableFactoryException}} will be thrown.
> User have no idea to know what is wrong.
> We can pick a best candidate to print where is wrong, print requiredContext
> and supportedProperties in different formats.
> In this way, users can know which property in requiredContext is lack, and
> which property is not allow in supportedProperties.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
