I'll try to answer some questions which I do not see answered above.
> GraphFrame is just a Graph Analytics/Query Engine, not a Graph Engine
which GraphX used to be.
GraphFrames supports all of the algorithms which GraphX supports. We've
also taken first steps towards providing primitives for pe
GraphFrame is just a Graph Analytics/Query Engine, not a Graph Engine which
GraphX used to be.
And I'm sorry to say, it doesn’t fit most scenarioes at all in fact.
Enzo, I don’t think there is any roadmap of Graph libraries for Spark for
now.
*Andy*
On Tue, Mar 14, 2017 at 7:28 AM, Tim Hunter
Hello Enzo,
since this question is also relevant to Spark, I will answer it here. The
goal of GraphFrames is to provide graph capabilities along with excellent
integration to the rest of the Spark ecosystem (using modern APIs such as
DataFrames). As you seem to be well aware, a large number of gra
Since GraphFrames is not part of the Spark project, your
GraphFrames-specific questions are probably better directed at the
GraphFrames issue tracker:
https://github.com/graphframes/graphframes/issues
As far as I know, GraphFrames is an active project, though not as active as
Spark of course. The
Nick
Thanks for the quick answer :)
Sadly, the comment in the page doesn’t answer my questions. More specifically:
1. GraphFrames last activity in github was 2 months ago. Last release on 12
Nov 2016. Till recently 2 month was close to a Spark release cycle. Why there
has been no major deve
Your question is answered here under "Will GraphFrames be part of Apache
Spark?", no?
http://graphframes.github.io/#what-are-graphframes
Nick
On Mon, Mar 13, 2017 at 4:56 PM enzo wrote:
> Please see this email trail: no answer so far on the user@spark board.
> Trying the developer board for
