[
https://issues.apache.org/jira/browse/FLINK-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15261674#comment-15261674
]
ASF GitHub Bot commented on FLINK-3754:
---------------------------------------
Github user yjshen commented on the pull request:
https://github.com/apache/flink/pull/1916#issuecomment-215334972
@twalthr, translate table API call to `SqlNode` and use `validator` in
Calcite seems another reasonable solution, maybe it's hard to do `eager
validation` as @fhueske proposed?
Yes, I agree we should discuss which way is preferred solution :)
> Add a validation phase before construct RelNode using TableAPI
> --------------------------------------------------------------
>
> Key: FLINK-3754
> URL: https://issues.apache.org/jira/browse/FLINK-3754
> Project: Flink
> Issue Type: Improvement
> Components: Table API
> Affects Versions: 1.0.0
> Reporter: Yijie Shen
> Assignee: Yijie Shen
>
> Unlike sql string's execution, which have a separate validation phase before
> RelNode construction, Table API lacks the counterparts and the validation is
> scattered in many places.
> I suggest to add a single validation phase and detect problems as early as
> possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
