[
https://issues.apache.org/jira/browse/SPARK-15086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318157#comment-15318157
]
Sean Owen commented on SPARK-15086:
-----------------------------------
Before I get going, and after looking at the current Java API, I want to check
in about what the ideal outcome is.
JavaSparkContext has methods like intAccumulator. These should really be
longAccumulator now. Deprecate and add? or just remove intAccumulator to be
consistent with SparkContext.
JavaSparkContext has methods that take an initial value, like
doubleAccumulator(double). SparkContext's new API does not. Deprecate, remove?
In fact, the SparkContext API is usable in Java AFAICT. Is it worth maintaining
a Java wrapper or just deprecate the lot?
> Update Java API once the Scala one is finalized
> -----------------------------------------------
>
> Key: SPARK-15086
> URL: https://issues.apache.org/jira/browse/SPARK-15086
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Reporter: Reynold Xin
> Priority: Blocker
>
> We should make sure we update the Java API once the Scala one is finalized.
> This includes adding the equivalent API in Java as well as deprecating the
> old ones.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
