[jira] [Created] (FLINK-17952) Improve the error message when old planner and batch mode is used via EnvironmentSettings

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (FLINK-17952) Improve the error message when old planner and batch mode is used via EnvironmentSettings

Shang Yuanchun (Jira)
Dian Fu created FLINK-17952:
-------------------------------

             Summary: Improve the error message when old planner and batch mode is used via EnvironmentSettings
                 Key: FLINK-17952
                 URL: https://issues.apache.org/jira/browse/FLINK-17952
             Project: Flink
          Issue Type: Improvement
          Components: API / Python
    Affects Versions: 1.10.0, 1.9.0, 1.11.0
            Reporter: Dian Fu
             Fix For: 1.11.0


Currently it doesn't support to use batch mode of the old planner via EnvironmentSettings. The following message will be thrown in that case:
{code}
: org.apache.flink.table.api.NoMatchingTableFactoryException: Could not find a suitable table factory for 'org.apache.flink.table.delegation.ExecutorFactory' in: org.apache.flink.table.api.NoMatchingTableFactoryException: Could not find a suitable table factory for 'org.apache.flink.table.delegation.ExecutorFactory' inthe classpath.
Reason: No factory supports the additional filters.
The following properties are requested:class-name=org.apache.flink.table.executor.StreamExecutorFactorystreaming-mode=false
The following factories have been considered:org.apache.flink.table.planner.delegation.BlinkExecutorFactory at org.apache.flink.table.factories.ComponentFactoryService.find(ComponentFactoryService.java:71) at org.apache.flink.table.api.internal.TableEnvironmentImpl.create(TableEnvironmentImpl.java:253) at org.apache.flink.table.api.TableEnvironment.create(TableEnvironment.java:91) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.flink.api.python.shaded.py4j.reflection.MethodInvoker.invoke(MethodInvoker.java:244) at org.apache.flink.api.python.shaded.py4j.reflection.ReflectionEngine.invoke(ReflectionEngine.java:357) at org.apache.flink.api.python.shaded.py4j.Gateway.invoke(Gateway.java:282) at org.apache.flink.api.python.shaded.py4j.commands.AbstractCommand.invokeMethod(AbstractCommand.java:132) at org.apache.flink.api.python.shaded.py4j.commands.CallCommand.execute(CallCommand.java:79) at org.apache.flink.api.python.shaded.py4j.GatewayConnection.run(GatewayConnection.java:238) at java.lang.Thread.run(Thread.java:745)
{code}

This exception message is confusing for a Python users and we should improve it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)