[ 
https://issues.apache.org/jira/browse/SPARK-16693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392537#comment-15392537
 ] 

Felix Cheung edited comment on SPARK-16693 at 7/25/16 7:38 PM:
---------------------------------------------------------------

Deprecated methods because of Spark JVM API changes are only a very small 
subset (actually, there's only 1: registerTempTable), agreed we should 
coordinate with JVM side if we could.
There are bigger changes to SparkR specific APIs (sqlContext parameter removal, 
sparkR.init) I think would be very good to clean up soon. They present changes 
to behavior they would become harder to maintain over time.
SparkR API has been "experimental" so I didn't think there would be a big 
problem, but we could certainly wait to get some feedback.


was (Author: felixcheung):
Deprecated methods because of Spark JVM API changes are only a very small 
subset (3 methods), agreed we should coordinate with JVM side if we could.
There are bigger changes to SparkR specific APIs (sqlContext parameter removal, 
sparkR.init) I think would be very good to clean up soon. They present changes 
to behavior they would become harder to maintain over time.
SparkR API has been "experimental" so I didn't think there would be a big 
problem, but we could certainly wait to get some feedback.

> Remove R deprecated methods
> ---------------------------
>
>                 Key: SPARK-16693
>                 URL: https://issues.apache.org/jira/browse/SPARK-16693
>             Project: Spark
>          Issue Type: Bug
>          Components: SparkR
>    Affects Versions: 2.0.0
>            Reporter: Felix Cheung
>
> For methods deprecated in Spark 2.0.0, we should remove them in 2.1.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to