You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Sun Rui (JIRA)" <ji...@apache.org> on 2015/05/08 12:03:00 UTC

[jira] [Created] (SPARK-7482) Rename some DataFrame API methods in SparkR to match their counterparts in Scala

Sun Rui created SPARK-7482:
------------------------------

             Summary: Rename some DataFrame API methods in SparkR to match their counterparts in Scala
                 Key: SPARK-7482
                 URL: https://issues.apache.org/jira/browse/SPARK-7482
             Project: Spark
          Issue Type: Improvement
          Components: SparkR
    Affects Versions: 1.4.0
            Reporter: Sun Rui
            Priority: Critical


This is re-consideration on how to solve name conflict. Previously, we rename API names from Scala API if there is name conflict with base or other commonly-used packages. However, from long term perspective, this is not good for API stability, because we can't predict name conflicts, for example, if in the future a name added in base package conflicts with an API in SparkR? So the better policy is to keep API name same as Scala's without worrying about name conflicts. When users use SparkR, they should load SparkR as last package, so that all API names are effective. Use can explicitly use :: to refer to hidden names from other packages.

more discussion can be found at https://issues.apache.org/jira/browse/SPARK-6812




--
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