[
https://issues.apache.org/jira/browse/FLINK-10079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Zhang updated FLINK-10079:
------------------------------
Description:
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.
> Automatically register sink table from external catalogs
> --------------------------------------------------------
>
> 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.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)
