spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shivaram Venkataraman (JIRA)" <>
Subject [jira] [Commented] (SPARK-11886) R function name conflicts with base or stats package ones
Date Tue, 01 Dec 2015 00:49:10 GMT


Shivaram Venkataraman commented on SPARK-11886:

We can't really help this scenario -- Basically the package loaded last gets control of the
method and in this case the call to `select(DataFrame, 1)` is being captured by dplyr and
then forwarded to `select_`. AFAIK there is very little we can change in our definition of
`select` to avoid this. 

I'm more interested in the reverse -- if you load dplyr first and then load SparkR, does `select`
work on a local R data.frame ? This is something we can avoid breaking using our generics

> R function name conflicts with base or stats package ones
> ---------------------------------------------------------
>                 Key: SPARK-11886
>                 URL:
>             Project: Spark
>          Issue Type: Bug
>          Components: SparkR
>    Affects Versions: 1.5.2
>            Reporter: Felix Cheung
>            Priority: Minor
> See
> Currently these are masked:
> stats::cov
> stats::filter
> base::sample
> base::table
> [~shivaram] suggested:
> "
> If we have same name but the param types completely don't match (and no room for ...)
then we override those functions but (This is true for sample, table, cov right now I guess)
we should try to limit the number of functions where we do this. Also we should revisit some
of these to see if we can avoid it (for example table can be renamed ?)
> "

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message