The Java and Scala APIs are organized in different Maven modules and the
Scala APIs are based on the respective Java API.
The benefit of this design is to keep Scala dependencies out of the Java
APIs which is requested by many users.
The Java and Scala counterparts of the DataSet and DataStream
Hi, Till, Thanks for your clear reply.
In fact the API of Java and Scala are not coordinating. User are easy confused
by the Same class name of Java/Scala API such as `StreamExecutionEnvironment`.
Since Scala can do almost what Java can, Why not use Scala only? Kafka's API
looks good.
I think you're referring to the implementation of some of Flink's modules,
right?
If that is the case, then the rule of thumb is that we want to use Java for
the low level runtime implementations. For the API implementations it is a
case to case decision. The Scala API, for example is of course
Scala and Java mixed in the module. Some Flink API indeed make someone confused.
What is rule about the current Scala and Java API at the first implement time?
Thanks
