Github user yjshen commented on the pull request:
https://github.com/apache/flink/pull/1961#issuecomment-216877262
Hi @fhueske , thanks for the explanation. If I get it correctly, the
current `toSink` API is a general one to allow write table content to a large
variety of `Sinks` without blow up `flink-table` modules dependencies, the
design seems quite reasonable for me now.
BTW, if we are going to support some **native** output format, the
`register` & `reflection` seems a feasible approach, by doing this, we can not
only do
``` scala
t.toSink("csv").option("path", "/foo").option("fieldDelim", "|")
```
in Table API but also
``` sql
insert overwrite into parquet_table_a select * from table_b
```
in SQL.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
