You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Tzu-Li (Gordon) Tai (JIRA)" <ji...@apache.org> on 2018/12/17 16:02:01 UTC
[jira] [Updated] (FLINK-10079) Support external sink table in
INSERT INTO statement
[ https://issues.apache.org/jira/browse/FLINK-10079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tzu-Li (Gordon) Tai updated FLINK-10079:
----------------------------------------
Fix Version/s: (was: 1.6.3)
1.6.4
> Support external sink table in INSERT INTO statement
> ----------------------------------------------------
>
> Key: FLINK-10079
> URL: https://issues.apache.org/jira/browse/FLINK-10079
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Affects Versions: 1.6.0
> Reporter: Jun Zhang
> Assignee: Jun Zhang
> Priority: Major
> Fix For: 1.6.4, 1.8.0
>
>
> In the documentation, there is a description:
> {quote}Once registered in a TableEnvironment, all tables defined in a ExternalCatalog can be accessed from Table API or SQL queries by specifying their full path, such as catalog.database.table.
> {quote}
> Currently, this is true only for source tables. For sink table (specified in the Table API or SQL), the users have to explicitly register it even though it is defined in a registered ExternalCatalog, otherwise "No table was registered under the name XXX" TableException would be thrown.
> It would be better keep consistent between source table and sink table, and the users would enjoy more convenient approach to inserting into sink tables.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)