spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Cheung (JIRA)" <>
Subject [jira] [Commented] (SPARK-22281) Handle R method breaking signature changes
Date Sun, 22 Oct 2017 20:09:00 GMT


Felix Cheung commented on SPARK-22281:

tried a few things. If we remove the 

then cran checks fail with
* checking Rd \usage sections ... WARNING
Undocumented arguments in documentation object 'attach'
  ‘what’ ‘pos’ ‘name’ ‘warn.conflicts’

Functions with \usage entries need to have the appropriate \alias
entries, and all their arguments documented.
The \usage entries must correspond to syntactically valid R code.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.

if we change the method signature to

          signature(what = "SparkDataFrame"),
          function(what, ...) {

Then it fails to install
Error in rematchDefinition(definition, fdef, mnames, fnames, signature) :
  methods can add arguments to the generic ‘attach’ only if '...' is an argument to the
Error : unable to load R code in package ‘SparkR’
ERROR: lazy loading failed for package ‘SparkR’

> Handle R method breaking signature changes
> ------------------------------------------
>                 Key: SPARK-22281
>                 URL:
>             Project: Spark
>          Issue Type: Bug
>          Components: SparkR
>    Affects Versions: 2.2.1, 2.3.0
>            Reporter: Felix Cheung
> cAs discussed here
> this WARNING on R-devel
> * checking for code/documentation mismatches ... WARNING
> Codoc mismatches from documentation object 'attach':
> attach
>   Code: function(what, pos = 2L, name = deparse(substitute(what),
>                  backtick = FALSE), warn.conflicts = TRUE)
>   Docs: function(what, pos = 2L, name = deparse(substitute(what)),
>                  warn.conflicts = TRUE)
>   Mismatches in argument default values:
>     Name: 'name' Code: deparse(substitute(what), backtick = FALSE) Docs: deparse(substitute(what))
> Checked the latest release R 3.4.1 and the signature change wasn't there. This likely
indicated an upcoming change in the next R release that could incur this new warning when
we attempt to publish the package.
> Not sure what we can do now since we work with multiple versions of R and they will have
different signatures then.

This message was sent by Atlassian JIRA

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

View raw message