RyanSkraba opened a new pull request, #23006:
URL: https://github.com/apache/flink/pull/23006

   ## What is the purpose of the change
   
   * The entry points for using the Scala API were deprecated in 
https://github.com/apache/flink/pull/21176.  This PR ensures that all 
`@Public`, `@PublicEvolving` and `@Experimental` APIs are also marked as 
`@Deprecated`.
   * This PR doesn't have any code changes outside of deprecating these 
classes. Classes that are *not* scheduled for removal might still need to be 
migrated.
   
   ## Brief change log
   
   * All classes that contain one of those methods are also marked as 
deprecated with a link to 
[FLIP-265](https://cwiki.apache.org/confluence/display/FLINK/FLIP-265+Deprecate+and+remove+Scala+API+support).
   * The `flink-table`  modules have not been deprecated except for those 
dealing with a user-facing scala API (`flink-table-api-scala` and 
`flink-table-api-scala-bridge`)
   * The hadoop connector Scala classes were also `@Deprecated`
   
   ## Verifying this change
   
   This change is a trivial rework / code cleanup without any test coverage.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): **no**
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: **yes**
     - The serializers: **no**
     - The runtime per-record code paths (performance sensitive): **no**
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: **no**
     - The S3 file system connector: **no**
   
   ## Documentation
   
     - Does this pull request introduce a new feature? **no** (but it does 
prepare for the next major release as described in FLIP-265)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to