[
https://issues.apache.org/jira/browse/FLINK-32560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742015#comment-17742015
]
Ryan Skraba commented on FLINK-32560:
-------------------------------------
OK -- taking a quick look at the current work, I'll take a look at all modules
outside of table-planner and add the following annotation and comment *every
single time*:
{code}
/**
* @deprecated
* All Flink Scala APIs are deprecated and will be removed in a future Flink
version version. You
* can still build your application in Scala, but you should move to the Java
version of either
* the DataStream and/or Table API.
* @see
* <a
*
href="https://cwiki.apache.org/confluence/display/FLINK/FLIP-265+Deprecate+and+remove+Scala+API+support";>
* FLIP-265 Deprecate and remove Scala API support</a>
*/
@Deprecated
{code}
There's also some {{@Public}} scala code in flink-hadoop-compatibility, and
even if {{table-planner}} isn't in scope yet, the {{table-table-api-scala}} and
{{table-table-api-scala-bridge}} are likely also candidates for clean-up.
> Properly deprecate all Scala APIs
> ---------------------------------
>
> Key: FLINK-32560
> URL: https://issues.apache.org/jira/browse/FLINK-32560
> Project: Flink
> Issue Type: Sub-task
> Components: API / Scala
> Reporter: Xintong Song
> Assignee: Ryan Skraba
> Priority: Blocker
> Fix For: 1.18.0
>
>
> We agreed to drop Scala API support in FLIP-265 [1], and have tried to
> deprecate them in FLINK-29740. Also, both user documentation and roadmap[2]
> shows that scala API supports are deprecated. However, none of the APIs in
> `flink-streaming-scala` are annotated with `@Deprecated` atm, and only
> `ExecutionEnvironment` and `package` are marked `@Deprecated` in
> `flink-scala`.
> [1]
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-265+Deprecate+and+remove+Scala+API+support
> [2] https://flink.apache.org/roadmap/
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
