GitHub user jkbradley opened a pull request:

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

    [SPARK-5534] [graphx]  Graph getStorageLevel fix

    This fixes getStorageLevel for EdgeRDDImpl and VertexRDDImpl (and therefore 
for Graph).
    
    See code example on JIRA which failed before but works with this patch: 
[https://issues.apache.org/jira/browse/SPARK-5534]
    (The added unit tests also failed before but work with this fix.)
    
    Note: I used partitionsRDD, assuming that getStorageLevel will only be 
called on the driver.
    
    **QUESTION**: Please look at GraphSuite's test("cache, getStorageLevel").  
It succeeds, but should it?  After constructing the graph, vertices are cached, 
but edges are not.
    
    CC: @mengxr  (related to LDA PR), @rxin  @ankurdave   Thanks in advance!

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

    $ git pull https://github.com/jkbradley/spark graphx-storagelevel

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

    https://github.com/apache/spark/pull/4317.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 #4317
    
----
commit 17b488bb0cb5976e512f97cf9cf317de5dbf867f
Author: Joseph K. Bradley <[email protected]>
Date:   2015-02-02T22:26:44Z

    overrode getStorageLevel in Vertex/EdgeRDDImpl to use partitionsRDD

commit 18d64cacfba403041957743650b91a4e59677c6c
Author: Joseph K. Bradley <[email protected]>
Date:   2015-02-02T23:02:06Z

    Added tests for getStorageLevel in VertexRDDSuite, EdgeRDDSuite, GraphSuite

----


---
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