[
https://issues.apache.org/jira/browse/SPARK-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048039#comment-15048039
]
Felix Cheung commented on SPARK-12232:
--------------------------------------
WIP here:
https://github.com/felixcheung/spark/commit/999607180fa1a30b14a6e182f23aeb322c977cf5
It seems to be table() is a odd choice since it is about contingency table.
read.table() matches closer to our intend but by exporting it from SparkR it
makes base::read.table() inaccessible if calling without package:: prefix
(there is no S4 generics), which seems very bad to me that the user can't
create a data.frame.
Thought?
[~shivaram][~sunrui][~yanboliang]
> Consider exporting read.table in R
> ----------------------------------
>
> Key: SPARK-12232
> URL: https://issues.apache.org/jira/browse/SPARK-12232
> Project: Spark
> Issue Type: Bug
> Components: SparkR
> Affects Versions: 1.5.2
> Reporter: Felix Cheung
> Priority: Minor
>
> Since we have read.df, read.json, read.parquet (some in pending PRs), we have
> table() and we should consider having read.table() for consistency and
> R-likeness.
> However, this conflicts with utils::read.table which returns a R data.frame.
> It seems neither table() or read.table() is desirable in this case.
> table: https://stat.ethz.ch/R-manual/R-devel/library/base/html/table.html
> read.table:
> https://stat.ethz.ch/R-manual/R-devel/library/utils/html/read.table.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
