[
https://issues.apache.org/jira/browse/FLINK-10079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619847#comment-16619847
]
Fabian Hueske edited comment on FLINK-10079 at 9/19/18 8:01 PM:
----------------------------------------------------------------
Fixed for 1.6.2 with 65cd7b55eb7c0c7af840eebdddf83ae46d28e204
Fixed for 1.7.0 with cc37d7a7555aa7f18da2d0eb62c569cb080332ed
was (Author: fhueske):
Fixed for 1.6.2 with 57b621c8c1b39cbc42cca49212ba2b9bb7ef1a2b
Fixed for 1.7.0 with cc37d7a7555aa7f18da2d0eb62c569cb080332ed
> 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.7.0, 1.6.2
>
>
> 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)
