GitHub user mengxr opened a pull request:

    https://github.com/apache/spark/pull/16154

    [SPARK-17822] Make JVMObjectTracker a member variable of RBackend

    ## What changes were proposed in this pull request?
    
    * This PR changes `JVMObjectTracker` from `object` to `class` and let its 
instance associated with each RBackend. So we can manage the lifecycle of JVM 
objects when there are multiple `RBackend` sessions. `RBackend.close` will 
clear the object tracker explicitly.
    * I assume that `SQLUtils` and `RRunner` do not need to track JVM instances.
    * Small refactor of `SerDe.sqlSerDe` to increase readability.
    
    ## How was this patch tested?
    
    * Added unit tests for `JVMObjectTracker`.
    * Wait for Jenkins to run full tests.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mengxr/spark SPARK-17822

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/16154.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #16154
    
----
commit ede4242e8269e8dd8bcf458cdd47a5b8a42db33a
Author: Xiangrui Meng <[email protected]>
Date:   2016-12-05T17:13:53Z

    jvm object tracker should live inside RBackend

commit ca81b8cea3dc4b064a6d812132569c4f5f9425a6
Author: Xiangrui Meng <[email protected]>
Date:   2016-12-05T19:22:04Z

    Merge remote-tracking branch 'apache/master' into SPARK-17822

commit 801948ddcf471ec3bf1cdbc98c1be2590a756218
Author: Xiangrui Meng <[email protected]>
Date:   2016-12-05T19:53:39Z

    read also needs object tracker

commit 707613e8a2d5f3c3c608ba364662bee2000f9e7f
Author: Xiangrui Meng <[email protected]>
Date:   2016-12-05T20:40:22Z

    fix tests

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to