[
https://issues.apache.org/jira/browse/SPARK-16775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen updated SPARK-16775:
------------------------------
Affects Version/s: (was: 2.1.0)
3.0.0
Target Version/s: 3.0.0
Description:
Deprecating the old accumulator API added a large number of warnings - many of
these could be fixed with a bit of refactoring to offer a non-deprecated
internal class while still preserving the external deprecation warnings.
... but we can also just remove the old deprecated API entirely in Spark 3.0.0.
was:Deprecating the old accumulator API added a large number of warnings -
many of these could be fixed with a bit of refactoring to offer a
non-deprecated internal class while still preserving the external deprecation
warnings.
Summary: Remove deprecated accumulator v1 APIs (was: Reduce
internal warnings from deprecated accumulator API)
I'm hijacking this older Jira to be about just removing the old deprecated API
in Spark 3. At this point that's more likely to happen than cleaning up use of
the deprecated API.
> Remove deprecated accumulator v1 APIs
> -------------------------------------
>
> Key: SPARK-16775
> URL: https://issues.apache.org/jira/browse/SPARK-16775
> Project: Spark
> Issue Type: Improvement
> Components: PySpark, Spark Core, SQL
> Affects Versions: 3.0.0
> Reporter: holdenk
> Priority: Major
>
> Deprecating the old accumulator API added a large number of warnings - many
> of these could be fixed with a bit of refactoring to offer a non-deprecated
> internal class while still preserving the external deprecation warnings.
> ... but we can also just remove the old deprecated API entirely in Spark
> 3.0.0.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
