Timo Walther created FLINK-13350:
------------------------------------
Summary: Distinguish between temporary tables and persisted tables
Key: FLINK-13350
URL: https://issues.apache.org/jira/browse/FLINK-13350
Project: Flink
Issue Type: Bug
Components: Table SQL / API
Reporter: Timo Walther
Assignee: Timo Walther
Currently, there is no difference between temporary tables that are only
available to the current session and tables that need to be persisted in a
catalog. FLINK-13279 is an example for this shortcoming. Because we introduce
the first real catalog support in Flink 1.9, the difference becomes more
important to users.
A user must be able to express whether a table is just temporary or get an
exception if it can not be persisted as desired. Currently, non-persisted
tables are silently stored in a separate volatile data structure.
This issue might touch API, DDL, and SQL Client. We should discuss how we
approach this issue for the 1.9 release.
Some background information for people that would like to join the discussion:
MySQL:
https://dev.mysql.com/doc/refman/8.0/en/create-temporary-table.html
http://www.mysqltutorial.org/mysql-temporary-table/
Spark:
https://spark.apache.org/docs/latest/sql-getting-started.html#global-temporary-view
SQL Server:
https://docs.microsoft.com/en-us/sql/t-sql/statements/create-table-transact-sql?view=sql-server-2017
https://docs.microsoft.com/de-de/sql/relational-databases/databases/tempdb-database?view=sql-server-2017
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
