[
https://issues.apache.org/jira/browse/FLINK-10163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16584672#comment-16584672
]
Timo Walther commented on FLINK-10163:
--------------------------------------
[~suez1224] Yes, I think the full implementation as [~hequn8128] added it to
the issue should be done with the DDL FLIP. We need a proper parser for this
that also allows escaping like \{{CREATE VIEW `My Table Name`}} and specifying
optional column names and types. Also \{{DROP VIEW}} and \{{REPLACE VIEW}}.
This should be integrated with the Table API.
This issue descibes just a MVP solution for allowing the very basic
\{{CREATE_VIEW name AS query}} for the SQL Client. Because there is currently
no way of defining a similar functionality like
\{{tableEnv.registerTable("name", ...)}} in Table API.
> Support CREATE VIEW in SQL Client
> ---------------------------------
>
> Key: FLINK-10163
> URL: https://issues.apache.org/jira/browse/FLINK-10163
> Project: Flink
> Issue Type: New Feature
> Components: Table API & SQL
> Reporter: Timo Walther
> Assignee: Timo Walther
> Priority: Major
>
> The possibility to define a name for a subquery would improve the usability
> of the SQL Client. The SQL standard defines \{{CREATE VIEW}} for defining a
> virtual table.
>
> Example:
> {code}
> CREATE VIEW viewName
> [ '(' columnName [, columnName ]* ')' ]
> AS Query
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
