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 2022/01/19 13:14:00 UTC

[jira] [Closed] (FLINK-25609) Avoid creating temporary tables for inline tables

     [ https://issues.apache.org/jira/browse/FLINK-25609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timo Walther closed FLINK-25609.
--------------------------------
    Fix Version/s: 1.15.0
       Resolution: Fixed

Fixed in master: 50ff5084461c5dda106cefd53afeeff240c5b416

> Avoid creating temporary tables for inline tables
> -------------------------------------------------
>
>                 Key: FLINK-25609
>                 URL: https://issues.apache.org/jira/browse/FLINK-25609
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / API
>            Reporter: Timo Walther
>            Assignee: Francesco Guardiani
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.15.0
>
>
> Currently, inline tables such as {{fromDataStream}} or {{from(TableDescriptor)}} as well as {{toChangelogStream}} or {{Table.executeInsert(TableDescriptor)}} create an artifical temporary table with object identifier.
> This is due to Calcite that forces {{RelBuilder.scan}} to have an object identifier.
> Instead we should:
> - Create an internal {{RelOptTable}} that wraps {{CatalogTable}}
> - Various flavors of {{CatalogTable}} can store the {{DataStream}} object or information of the {{TableDescriptor.}}
> - Manually create {{LogicalTableScan}}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)