ns that
>>>> you may still access them by using the namespace prefix SparkR with three
>>>> colons, e.g. SparkR:::func(foo, bar).
>>>>
>>>> So a starting place for porting old SparkR scripts from before the
>>>> merge could be to identif
ace identifier tacked on the front. I
>>> hope that helps.
>>>
>>> Regards,
>>> Alek Eskilson
>>>
>>> From: Andrew Psaltis
>>> Date: Monday, May 25, 2015 at 6:25 PM
>>> To: "dev@spark.apache.org"
>>> Subject:
they have the namespace identifier tacked on the front. I
>> hope that helps.
>>
>> Regards,
>> Alek Eskilson
>>
>> From: Andrew Psaltis
>> Date: Monday, May 25, 2015 at 6:25 PM
>> To: "dev@spark.apache.org"
>> Subject: SparkR and RDDs
>
skilson
>
> From: Andrew Psaltis
> Date: Monday, May 25, 2015 at 6:25 PM
> To: "dev@spark.apache.org"
> Subject: SparkR and RDDs
>
> Hi,
> I understand from SPARK-6799[1] and the respective merge commit [2] that
> the RDD class is private in Spark 1.4 . If
Date: Monday, May 25, 2015 at 6:25 PM
To: "dev@spark.apache.org<mailto:dev@spark.apache.org>"
mailto:dev@spark.apache.org>>
Subject: SparkR and RDDs
Hi,
I understand from SPARK-6799[1] and the respective merge commit [2] that the
RDD class is private in Spark 1.4 . If I wa
Hi,
I understand from SPARK-6799[1] and the respective merge commit [2] that
the RDD class is private in Spark 1.4 . If I wanted to modify the old
Kmeans and/or LR examples so that the computation happened in Spark what is
the best direction to go? Sorry if I am missing something obvious, but
base
