You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Marko A. Rodriguez (JIRA)" <ji...@apache.org> on 2015/05/26 16:49:17 UTC

[jira] [Created] (TINKERPOP3-703) Provide a "INPUT_GRAPH_RDD_CLASS" for SparkGraphComputer vendors.

Marko A. Rodriguez created TINKERPOP3-703:
---------------------------------------------

             Summary: Provide a "INPUT_GRAPH_RDD_CLASS" for SparkGraphComputer vendors.
                 Key: TINKERPOP3-703
                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-703
             Project: TinkerPop 3
          Issue Type: Improvement
          Components: hadoop
            Reporter: Marko A. Rodriguez
            Assignee: Marko A. Rodriguez


If a vendor has a direct Spark connector to their database, then they should be able to bypass using an {{InputFormat}} to construct the {{graphRDD}}. It would be cool to have a configuration option that is {{INPUT_GRAPH_RDD_CLASS}}.

{code}
Class<BiFunction<SparkContext,Configuration,JavaPairRDD<Object,VertexWritable>>
{code}

This way, the SparkGraphComputer code would be like:

{code}
if(configuration.hasProperty(INPUT_GRAPH_RDD_CLASS)) {
 Class<BiFunction<SparkContext,Configuration,JavaPairRDD<Object,VertexWritable>> theClass = Class.forName(configuration.get(INPUT_GRAPH_RDD_CLASS)).newInstance();
  graphRDD = theClass.apply(sparkContext,configuration);
} else {
  graphRDD = // use input format
}
{code}



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