[
https://issues.apache.org/jira/browse/FLINK-24338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17418607#comment-17418607
]
Ingo Bürk commented on FLINK-24338:
-----------------------------------
For a basic yes/no answer, the EXPLAIN solution would probably work well.
I agree that we need a proper validation mechanism to allow building tooling
around Flink SQL. Proper validation should also return detailed error details
such as Line/column number when possible. There's also different levels of
validation, i.e. purely on the syntax level, or including logical validation of
whether a table exists, or can even be instantiated, same for functions etc.
We'd probably have to expose these different levels separately as validating
the existence of a table might not always be desired.
There's also the question of validating several statements at once, eg some DDL
to create a table and then a query on that table. This is even trickier because
the validation of the query depends on the side effects of the first statement.
Even purely syntactical validation using the parser currently isn't possible
due to side effects performed in the parser. This is a technical debt that
would have to be resolved and requires changing the design of many Operation
subclasses.
> Provide an interface to validate flinksql
> -----------------------------------------
>
> Key: FLINK-24338
> URL: https://issues.apache.org/jira/browse/FLINK-24338
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / API
> Reporter: Spongebob
> Priority: Minor
>
> It would be great if there is an interface that can validate flinksql.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
