[jira] [Comment Edited] (SPARK-16088) Deprecate setJobGroup, clearJobGroup, cancelJobGroup from SparkR API

["Felix Cheung (JIRA)" <ji...@apache.org>]

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

Felix Cheung edited comment on SPARK-16088 at 6/21/16 7:10 AM:
---------------------------------------------------------------

It's possible - both setLogLevel and spark.lapply are new in 2.0.0, so it's very easy just to remove the sc parameter.

These have been around so should we simply remove the sc parameter from the signature? These are S3 methods so it could break people. To make it back compatible we would code to check parameter type and so on, similar to sqlContext methods we did in 2.0.0 except we would need a bunch of new code for sc instead.


was (Author: felixcheung):
It's possible - both setLogLevel and spark.lapply are new in 2.0.0, so it's very easy just to remove the sc parameter.

These have been around so should we simply remove the sc parameter from the signature? These are S3 methods so it could break people. To make it back compatible we would code to check parameter type and so on, similar to sqlContext methods we did in 2.0.0 except this would be for sc instead.

> Deprecate setJobGroup, clearJobGroup, cancelJobGroup from SparkR API
> --------------------------------------------------------------------
>
>                 Key: SPARK-16088
>                 URL: https://issues.apache.org/jira/browse/SPARK-16088
>             Project: Spark
>          Issue Type: Bug
>          Components: SparkR
>    Affects Versions: 1.6.1
>            Reporter: Felix Cheung
>
> Since they uses SparkContext?



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org