You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Timo Walther (JIRA)" <ji...@apache.org> on 2019/07/30 09:55:00 UTC

[jira] [Comment Edited] (FLINK-13461) Distinguish between temporary tables and persisted tables

    [ https://issues.apache.org/jira/browse/FLINK-13461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16895976#comment-16895976 ] 

Timo Walther edited comment on FLINK-13461 at 7/30/19 9:54 AM:
---------------------------------------------------------------

[Per discussion on the dev@ ML|http://mail-archives.apache.org/mod_mbox/flink-dev/201907.mbox/%3ce22331ca-00f3-fbdb-e4cf-671959b9322c@apache.org%3e] we will postpone this issue to Flink 1.10. Thus, not a blocker anymore for 1.9.


was (Author: twalthr):
[Per discussion on the dev@ ML|http://mail-archives.apache.org/mod_mbox/flink-dev/201907.mbox/%3ce22331ca-00f3-fbdb-e4cf-671959b9322c@apache.org%3e] we will postpone this issue to Flink 1.10. Thus, not a blocker anymore.

> Distinguish between temporary tables and persisted tables
> ---------------------------------------------------------
>
>                 Key: FLINK-13461
>                 URL: https://issues.apache.org/jira/browse/FLINK-13461
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / API
>            Reporter: Dawid Wysakowicz
>            Assignee: Dawid Wysakowicz
>            Priority: Blocker
>             Fix For: 1.10.0
>
>
> 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)