You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jark Wu (Jira)" <ji...@apache.org> on 2019/12/18 07:49:00 UTC
[jira] [Resolved] (FLINK-15232) Message of
NoMatchingTableFactoryException should tell users what's wrong
[ https://issues.apache.org/jira/browse/FLINK-15232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jark Wu resolved FLINK-15232.
-----------------------------
Resolution: Fixed
1.11.0: 781a7c85e7b476762aa2b921276ab36f11c85312
1.10.0: a879535a5afaee1c63bbbbfb36e2b49eb73e2707
> Message of NoMatchingTableFactoryException should tell users what's wrong
> -------------------------------------------------------------------------
>
> Key: FLINK-15232
> URL: https://issues.apache.org/jira/browse/FLINK-15232
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / API
> Reporter: Jingsong Lee
> Assignee: Jingsong Lee
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> 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)