[
https://issues.apache.org/jira/browse/FLINK-29739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17881486#comment-17881486
]
lincoln lee commented on FLINK-29739:
-------------------------------------
We've been working on code cleanup for the deprecated api related to FLIP-265
(including the scala table api), and it's expected to have it done by 9/30 in
time for the planned 2.0-preview release.
After reading this early message, my first thought is that if we can keep the
scala table api with lower maintenance cost, it will be helpful for scala api
users.
However, my colleague encountered some problems when trying to do the related
migration, which involves the code of flink scala api that will be deleted, one
way to deal with it is to move all the dependent code to scala table api, but
it may make this module become less lightweight and increase the maintenance
cost afterwards. [~yyhx] [~xuyangzhong] can you help to add more details?
Since this is a message from almost 2 years ago and we haven't found any more
follow up discussions, I'd like to ask you both what you think so far?
[~twalthr] [~martijnvisser]
> [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
> Labels: 2.0-related
>
> 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)
