[
https://issues.apache.org/jira/browse/FLINK-17303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17116405#comment-17116405
]
Dian Fu commented on FLINK-17303:
---------------------------------
[~hequn8128] Could we also backport this to 1.11.0 as:
- It was originally in 1.11.0 and we just revert it because the added tests are
not stable and so I think it should be fine to add it back to 1.11.0 after we
fixed the test stability issue [~zjwang] What's your thought?
- It affects the usability of a few APIs such as "execute_sql" a lot without
this PR as they will have to return a Java TableResult object instead of a
Python TableResult object. Python users are not aware of this and they have to
lookup the Java docs to know how to use these Python APIs. Besides, it
introduces potential backward compatibility issues between 1.11 and 1.12.
What's your thought?
> Return TableResult for Python TableEnvironment
> ----------------------------------------------
>
> Key: FLINK-17303
> URL: https://issues.apache.org/jira/browse/FLINK-17303
> Project: Flink
> Issue Type: Improvement
> Components: API / Python
> Reporter: godfrey he
> Assignee: Nicholas Jiang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.0
>
>
> [FLINK-16366|https://issues.apache.org/jira/browse/FLINK-16366] supports
> executing a statement and returning a {{TableResult}} object, which could get
> {{JobClient}} (to associates the submitted Flink job), collect the execution
> result, or print the execution result. In Python, we should also introduce
> python TableResult class to make sure consistent with Java.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
