: [Spark R] Proposal: Exposing RBackend in RRunner
Use case is to cache a reference to the JVM object created by SparkR.
On Wed, Mar 28, 2018 at 12:03 PM Reynold Xin
mailto:r...@databricks.com>> wrote:
If you need the functionality I would recommend you just copying the code over
to your proje
mple
>>
>> _
>> From: Jeremy Liu
>> Sent: Tuesday, March 27, 2018 12:20 PM
>> Subject: Re: [Spark R] Proposal: Exposing RBackend in RRunner
>> To:
>>
>>
>>
>> Spark Dev,
>>
>> On second though
aborate what you need JVMObjectTracker for? We have provided R
> convenient APIs to call into JVM: sparkR.callJMethod for example
>
> _
> From: Jeremy Liu
> Sent: Tuesday, March 27, 2018 12:20 PM
> Subject: Re: [Spark R] Proposal: Exposing RBackend in RR
: Tuesday, March 27, 2018 12:20 PM
Subject: Re: [Spark R] Proposal: Exposing RBackend in RRunner
To:
Spark Dev,
On second thought, the below topic seems more appropriate for spark-dev rather
than spark-users:
Spark Users,
In SparkR, RBackend is created in RRunner.main(). This in particular makes it
Spark Dev,
On second thought, the below topic seems more appropriate for spark-dev
rather than spark-users:
Spark Users,
>
> In SparkR, RBackend is created in RRunner.main(). This in particular makes
> it difficult to control or use the RBackend. For my use case, I am looking
> to access the JVMO
