Github user fhueske commented on a diff in the pull request:

    https://github.com/apache/flink/pull/1205#discussion_r41284498
  
    --- Diff: docs/libs/gelly_guide.md ---
    @@ -194,6 +194,27 @@ val edgeTuples = env.readCsvFile[String, String, 
Double]("path/to/edge/input")
     
     val graph = Graph.fromTupleDataSet(vertexTuples, edgeTuples, env)
     {% endhighlight %}
    +
    +* from a CSV file of Edge data and an optional CSV file of Vertex data. In 
this case, Gelly will convert each row from the Edge CSV file to an `Edge`, 
where the first field will be the source ID, the second field will be the 
target ID and the third field (if present) will be the edge value. 
Equivalently, each row from the optional Vertex CSV file will be converted to a 
`Vertex`, where the first field will be the vertex ID and the second field (if 
present) will be the vertex value.
    +If the vertices have no associated value, set the `vertexValue` parameter 
to `false`. If the edges have no associated value, set the `edgeValue` 
parameter to `false`.
    +
    +{% highlight scala %}
    +val env = ExecutionEnvironment.getExecutionEnvironment
    +
    +// create a Graph with String Vertex IDs, Long Vertex values and Double 
Edge values
    +val graph = Graph.fromCsvReader[String, Long, Double](
    +           pathVertices = "path/to/vertex/input",
    +           pathEdges = "path/to/edge/input",
    +           env = env)
    +
    +
    +// create a Graph with neither Vertex nor Edge values
    +val simpleGraph = Graph.fromCsvReader[Long, NullValue, NullVale](
    +           vertexValue = false,
    --- End diff --
    
    Is it necessary to set `vertexValue` to false if no vertex path is 
specified?


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

Reply via email to