Github user kdatta commented on the pull request:

    https://github.com/apache/spark/pull/4205#issuecomment-71556164
  
    Hi All,
    
    Here's what I suggest we do:
    1. Complete a design document on PyGraphX and attach it to JIRA
    2. Wait for Java API for GraphX to be resolved i.e. pull request #3234.
    There's no way out of this and no reason for duplication of effort.
    3. Remove Java API of GraphX from pull request #4205 and build with #3234
    instead.
    4. Create new pull request for PyGraphX
    
    
    On Mon, Jan 26, 2015 at 1:58 PM, Patrick Wendell <notificati...@github.com>
    wrote:
    
    > Hey all, I'd like to close this issue and defer to a design doc before
    > there is a lot of commenting on this. This pulls in another patch that is
    > itself not merged and major portions of the PySpark API are copy/pasted.
    > For instance, it might be good to wait until #3234
    > <https://github.com/apache/spark/pull/3234> is merged before asking for a
    > lot of community review here.
    >
    > —
    > Reply to this email directly or view it on GitHub
    > <https://github.com/apache/spark/pull/4205#issuecomment-71547165>.
    >


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to