g; dev@spark.apache.org
Subject: Re: [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
<r...@databricks.com<mailto:r...@databricks.com>> wrote:
If you need the functionality I w
gt;> convenient APIs to call into JVM: sparkR.callJMethod for example
>>
>> _
>> From: Jeremy Liu <jeremy.jl....@gmail.com>
>> Sent: Tuesday, March 27, 2018 12:20 PM
>> Subject: Re: [Spark R] Proposal: Exposing RBackend in RRunner
>>
ic to SparkR.
>
> Can you elaborate what you need JVMObjectTracker for? We have provided R
> convenient APIs to call into JVM: sparkR.callJMethod for example
>
> _
> From: Jeremy Liu <jeremy.jl@gmail.com>
> Sent: Tuesday, March 27, 2018 12:
.jl@gmail.com>
Sent: Tuesday, March 27, 2018 12:20 PM
Subject: Re: [Spark R] Proposal: Exposing RBackend in RRunner
To: <dev@spark.apache.org>
Spark Dev,
On second thought, the below topic seems more appropriate for spark-dev rather
than spark-users:
Spark Users,
In SparkR, RBacken
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
