[
https://issues.apache.org/jira/browse/FLINK-10061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16571417#comment-16571417
]
Fabian Hueske commented on FLINK-10061:
---------------------------------------
Actually, I think we should drop the {{Table.writeToSink(TableSink)}} method
and refer users to use {{insertInto(String)}} to emit a table to a registered
sink table.
1. {{writeToSink()}} was added as a workaround when we didn't support
registration of sinks and {{INSERT INTO SELECT}} queries yet.
2. I don't like the idea of handling built-in and custom sinks separately. The
recently introduced connector, format, and schema descriptors significantly
ease the definition of built-in connectors.
3. This approach is more aligned with SQL and IMO more principled because it
uses doesn't require to use TableSinks once they are registered in the
TableEnvironment.
Best, Fabian
> Fix unsupported reconfiguration in KafkaTableSink
> -------------------------------------------------
>
> Key: FLINK-10061
> URL: https://issues.apache.org/jira/browse/FLINK-10061
> Project: Flink
> Issue Type: Bug
> Components: Kafka Connector
> Affects Versions: 1.6.0
> Reporter: Jun Zhang
> Assignee: Jun Zhang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.1, 1.7.0
>
>
> When using KafkaTableSink in "table.writeToSink(), the following exception is
> thrown:
> {quote} java.lang.UnsupportedOperationException: Reconfiguration of this sink
> is not supported.
> {quote}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
