gradoop icon indicating copy to clipboard operation
gradoop copied to clipboard

Published 20 hours ago • verified publisher icon dbs-leipzig

Implement tuple based Gradoop model

Open s1ck opened this issue 10 years ago • 3 comments
trafficstars

Currently, model entities (vertices, edges, logical graphs) are represented as Pojos. We want to evaluate the performance compared to tuple implementations. Tuple classed need to use interface located in gradoop-core as those are used by the persistence layer.

s1ck avatar Oct 06 '15 13:10 s1ck

a good stragey could be the implementation of the existing VertexData, EdgeData and GraphData interfaces by Tuple types in addition to the Pojo-Implementations. This way, both variants are interchangeable which allows us to test performance.

s1ck avatar Oct 06 '15 16:10 s1ck

@p3et in #90, I replaced the internal gelly graph with dedicated DataSets for VD, ED and GD. This could be a good starting point to add alternative (tuple) implementations without breaking everything.

s1ck avatar Oct 26 '15 12:10 s1ck

I implemented tuple versions of the EPGM interfaces. However, this lead to problems with field forwarding and field access via name. A class extending a tuple and fulfilling the pojo contract is not supported by the field name access methods of flink.

s1ck avatar Jul 28 '16 14:07 s1ck