Thanks, then let's revisit this in a bit when the Blink/Flink runners have
been separated in their package structure.
On Wed, Jun 12, 2019 at 2:04 PM Aljoscha Krettek
wrote:
> +1 I agree that Table API should be in lib because it will become a
> first-class-citizen.
>
> Currently, both the
+1 I agree that Table API should be in lib because it will become a
first-class-citizen.
Currently, both the classic Flink Table Runner and the new Blink-based Table
Runner share the same package structure, i.e they are both rooted in
org.apache.flink.table. We have to resolve this before we
Given that the Table API is going to be Flink's main API for analytical
workloads, it makes sense to make it as easy as possible for users to
actually use it.
The question I would have is which other transitive dependencies are we
gonna add to Flink's system class path by adding the Table API
Hi all!
I want to discuss making the Table API jars part of the "flink uber jar" in
"/lib" by default.
So far, the Table API was an optional dependency in "/opt".
With the current effort to make it a first class API in Flink, it would be
good experience if the Table API was available by default.
