Timo Walther created FLINK-8831:
-----------------------------------
Summary: Create SQL Client dependencies
Key: FLINK-8831
URL: https://issues.apache.org/jira/browse/FLINK-8831
Project: Flink
Issue Type: New Feature
Components: Table API & SQL
Reporter: Timo Walther
Assignee: Timo Walther
A first minimum version of FLIP-24 for the upcoming
Flink SQL Client has been merged to the master. We also merged
possibilities to discover and configure table sources without a single
line of code using string-based properties and Java service provider
discovery.
We are now facing the issue of how to manage dependencies in this new
environment. It is different from how regular Flink projects are created
(by setting up a a new Maven project and build a jar or fat jar).
Ideally, a user should be able to select from a set of prepared
connectors, catalogs, and formats. E.g., if a Kafka connector and Avro
format is needed, all that should be required is to move a
"flink-kafka.jar" and "flink-avro.jar" into the "sql_lib" directory that
is shipped to a Flink cluster together with the SQL query.
[As discussed on
ML|http://mail-archives.apache.org/mod_mbox/flink-dev/201802.mbox/%3C9c73518b-ec8e-3b01-f200-dea816c75efc%40apache.org%3E],
we will build fat jars for these modules with every Flink release that can be
hostet somewhere (e.g. Apache infrastructure, but not Maven central). This
would make it very easy to add a dependency by downloading the prepared JAR
files.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
