srowen opened a new pull request #25558: 
[SPARK-28855][CORE][ML][SQL][STREAMING] Remove outdated usages of Experimental, 
Evolving annotations
URL: https://github.com/apache/spark/pull/25558
 
 
   ### What changes were proposed in this pull request?
   
   The Experimental and Evolving annotations are both (like Unstable) used to 
express that a an API may change. However there are many things in the code 
that have been marked that way since even Spark 1.x. Per the dev@ thread, 
anything introduced at or before Spark 2.3.0 is pretty much 'stable' in that it 
would not change without a deprecation cycle. Therefore I'd like to remove most 
of these annotations. And, remove the `:: Experimental ::` scaladoc tag too. 
And likewise for Python, R.
   
   The changes below can be summarized as:
   - Generally, anything introduced at or before Spark 2.3.0 has been unmarked 
as neither Evolving nor Experimental
   - Obviously experimental items like DSv2, Barrier mode, ExperimentalMethods 
are untouched
   - I _did_ unmark a few MLlib classes introduced in 2.4, as I am quite 
confident they're not going to change (e.g. KolmogorovSmirnovTest, 
PowerIterationClustering)
   
   It's a big change to review, so I'd suggest scanning the list of _files_ 
changed to see if any area seems like it should remain partly experimental and 
examine those.
   
   ### Why are the changes needed?
   
   Many of these annotations are incorrect; the APIs are de facto stable. 
Leaving them also makes legitimate usages of the annotations less meaningful.
   
   ### Does this PR introduce any user-facing change?
   
   No.
   
   ### How was this patch tested?
   
   Existing tests.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to