Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Eduardo Pareja Tobes
    @eparejatobes
    nice!
    Alexey Alekhin
    @laughedelic
    @alberskib :wink: Happy birthday, Bart! :tada::confetti_ball::tada:
    alberskib
    @alberskib
    @laughedelic Thank you very much :smile:. It is really nice!
    Alexey Alekhin
    @laughedelic
    :blush:
    alberskib
    @alberskib
    Hey. I just want to inform that for two weeks I must suspend work(master thesis). I will start from 29.12
    Eduardo Pareja Tobes
    @eparejatobes
    @alberskib fine, good luck with it!
    alberskib
    @alberskib
    @/all Hey guys!
    First of all I would like to tell you that I am feeling terrible that I was constantly saying that I am starting but I did not produce any progress. Sorry for that!
    Today I come back and I will do everything(I have job so I will be working mostly on evenings and weekends) to deliver first version as soon as possible. From now I am starting work on that (regularly) to deliver systematicly product increments. I think that at some point I will need little help from you.
    One more time sorry for that.
    alberskib
    @alberskib
    Hey. I think that I am missing part of big picture - as a result I have next questions:
    1. Do I need to override TypedEdge, TypedVertex in order to provide specific versions for DynamoDb backend or just implement some kind of DynamoDbRawVertex, DynamoDbRawEdge. I am not sure: I think that yes I need to, but when I look into titan or neo4j implementation of angulillos there is no such files.
    2. I in TypedEdge and TypedVertex is just for identifying used backend and offer possibility to communicate graphs from different backends?
    Eduardo Pareja Tobes
    @eparejatobes
    hey @alberskib sorry missed this
    gitter notifications are pretty buggy
    Eduardo Pareja Tobes
    @eparejatobes
    You don't need to override anything
    First, all the actual interaction happens at the UntypedGraph level
    You do need to define classes like DynamoDBRawVertex, DynamoDBRawVertexType, etc
    Eduardo Pareja Tobes
    @eparejatobes
    In the case of Titan, they're already provided by Titan; we're just reusing TitanVertex, VertexLabelMaker, etc.
    As here we're free to implement all those things as we please, we can take a more reasonable approach.
    Eduardo Pareja Tobes
    @eparejatobes
    DynamoDBRawVertexType for example should have a link to the corresponding DynamoDB tables used to store the vertices; DynamoDBRawEdgeType should have refs to the corresponding source and target raw types, together will all the edge-specific tables
    Tables means just table names, of course
    All the XXXType classes should be completely decoupled from any resource management, auth etc.
    That should be at the untyped graph level
    About raw edges and vertices, they should have just a link to the corresponding type together with something identifying them (the property id used in the corresponding table , for example)
    You could implement everything then at the untyped graph level
    retrieving things from DynamoDB etc
    also, any stuff like caching of properties etc should go there I think
    alberskib
    @alberskib
    Hey @eparejatobes, Great to know
    Eduardo Pareja Tobes
    @eparejatobes
    no problem, if there's something else just ask! :)