[jira] [Assigned] (SPARK-7482) Rename some DataFrame API methods in SparkR to match their counterparts in Scala
[ https://issues.apache.org/jira/browse/SPARK-7482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-7482: --- Assignee: (was: Apache Spark) > 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-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Assigned] (SPARK-7482) Rename some DataFrame API methods in SparkR to match their counterparts in Scala
[ https://issues.apache.org/jira/browse/SPARK-7482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-7482: --- Assignee: Apache Spark > 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 >Assignee: Apache Spark >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-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
