You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@spark.apache.org by Colin Gillespie <cs...@gmail.com> on 2015/08/25 19:26:50 UTC
SparkR: exported functions
Hi,
I've just started playing about with SparkR (Spark 1.4.1), and noticed
that a number of the functions haven't been exported. For example,
the textFile function
https://github.com/apache/spark/blob/master/R/pkg/R/context.R
isn't exported, i.e. the function isn't in the NAMESPACE file. This is obviously
due to the ' missing in the roxygen2 directives.
Is this intentional?
Thanks
Colin
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@spark.apache.org
For additional commands, e-mail: user-help@spark.apache.org
RE: SparkR: exported functions
Posted by Felix Cheung <fe...@hotmail.com>.
I believe that is done explicitly while the final API is being figured out.
For the moment you could use DataFrame read.df()
> From: csgillespie@gmail.com
> Date: Tue, 25 Aug 2015 18:26:50 +0100
> Subject: SparkR: exported functions
> To: user@spark.apache.org
>
> Hi,
>
> I've just started playing about with SparkR (Spark 1.4.1), and noticed
> that a number of the functions haven't been exported. For example,
> the textFile function
>
> https://github.com/apache/spark/blob/master/R/pkg/R/context.R
>
> isn't exported, i.e. the function isn't in the NAMESPACE file. This is obviously
> due to the ' missing in the roxygen2 directives.
>
> Is this intentional?
>
> Thanks
>
> Colin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@spark.apache.org
> For additional commands, e-mail: user-help@spark.apache.org
>