[
https://issues.apache.org/jira/browse/FLINK-29739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17625534#comment-17625534
]
Timo Walther commented on FLINK-29739:
--------------------------------------
Sorry, to jump into this topic so late. But I just wanted to express my
personal opinion that we might be a bit too strict here. For DataStream API, it
makes absolutely sense to drop the stack due to lack of macro support, state
incompatibilities, etc. However, for Table API, we have put in significant
effort to support Scala, Kotlin, etc. long-term without larger maintenance
overhead. They only add some cherries on top of the cake with minimal code.
Mostly adding some implicits to the otherwise full Java implementation. Given
that Table API is the API with the highest abstraction, I would still vote for
keeping the Scala Table API. Of course I'm biased emotionally here, but also
from a technical point of view, all mentioned arguments mostly refer to
DataStream API, not Table API which has been designed from the mistakes of the
past.
> [FLIP-265] Deprecate and remove Scala API support
> -------------------------------------------------
>
> Key: FLINK-29739
> URL: https://issues.apache.org/jira/browse/FLINK-29739
> Project: Flink
> Issue Type: Technical Debt
> Components: API / Scala
> Reporter: Martijn Visser
> Priority: Major
>
> FLIP:
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-265+Deprecate+and+remove+Scala+API+support
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
