You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2017/03/03 11:59:45 UTC
[jira] [Commented] (SPARK-16775) Reduce internal warnings from
deprecated accumulator API
[ https://issues.apache.org/jira/browse/SPARK-16775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894209#comment-15894209 ]
Sean Owen commented on SPARK-16775:
-----------------------------------
Are there still areas where uses of deprecated accumulators can be changed? I'm aware they're still referenced from tests, but they kind of have to be in at least most of those cases.
> Reduce internal warnings from deprecated accumulator API
> --------------------------------------------------------
>
> Key: SPARK-16775
> URL: https://issues.apache.org/jira/browse/SPARK-16775
> Project: Spark
> Issue Type: Improvement
> Components: PySpark, Spark Core, SQL
> Affects Versions: 2.1.0
> Reporter: holdenk
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org