Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-13461 Distinguish between temporary tables and persisted tables
  3. FLINK-13350

Mark useCatalog & useDatabase as Experimental for 1.9 release

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • None
    • 1.9.0
    • Table SQL / API
    • None

    Description

      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

      Attachments

        Issue Links

          Activity

            People

              dwysakowicz Dawid Wysakowicz
              twalthr Timo Walther
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: