[ 
https://issues.apache.org/jira/browse/SPARK-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333265#comment-14333265
 ] 

lukovnikov commented on SPARK-5940:
-----------------------------------

Probably it's better to involve core Spark/GraphX developers here as well, 
especially for the refactoring part.

Anyway, from my part, I'd love to have loaders (and savers) for different RDF 
formats and (sparse) matrix/tensor formats (for scipy/...).

As for the refactoring, I'd guess it would make sense to have a loader 
interface with a load() method and a facade combining different loader 
interface implementations (so it would have methods like loadNT(), loadEdges(), 
loadTTL(),...).

> Graph Loader: refactor + add more formats
> -----------------------------------------
>
>                 Key: SPARK-5940
>                 URL: https://issues.apache.org/jira/browse/SPARK-5940
>             Project: Spark
>          Issue Type: New Feature
>          Components: GraphX
>            Reporter: lukovnikov
>            Priority: Minor
>
> Currently, the only graph loader is GraphLoader.edgeListFile. [SPARK-5280] 
> adds a RDF graph loader.
> However, as Takeshi Yamamuro suggested on github [SPARK-5280], 
> https://github.com/apache/spark/pull/4650, it might be interesting to make 
> GraphLoader an interface with several implementations for different formats. 
> And maybe it's good to make a façade graph loader that provides a unified 
> interface to all loaders.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to