33 replies

Isolated vertices vs connected vertices with no join benefit

Is there any downside to storing an isolated vertex with references to other nodes? Creating relationships makes the query more complicated than it needs to be, but storing references to other vertices seems like an anti-pattern/smell.
The relationship between nodes is defined as follows:

g.addV('batch').property(id,'batch-a').as('a').
  addV('batch').property(id,'batch-b')as('b').
  addV('reusable').property(id, 123).as('r1').
  addV('reusable').property(id, 123).as('r2').
  addE('link').from('a').to('r').
  addE('link').from('b').to('r2').iterate()

g.addV('batch').property(id,'batch-a').as('a').
  addV('batch').property(id,'batch-b')as('b').
  addV('reusable').property(id, 123).as('r1').
  addV('reusable').property(id, 123).as('r2').
  addE('link').from('a').to('r').
  addE('link').from('b').to('r2').iterate()

g.addV('connected').property('property", 'abc').as('coonected-v).addE('relates_to_batch').from('connected-a).to('batch-a').addE('related_to_reusable').from('connected-a').to('r1).iterate()

g.addV('connected').property('property", 'abc').as('coonected-v).addE('relates_to_batch').from('connected-a).to('batch-a').addE('related_to_reusable').from('connected-a').to('r1).iterate()

Querying this looks like:

g.V('batch-a').project('batchId', 'reusableId', 'connected').by(T.id).by(__.in('relates_to_batch').out("relates_to_reusable").id()).by(__.in("relates_to_batch").elementMap().fold()).toList()

g.V('batch-a').project('batchId', 'reusableId', 'connected').by(T.id).by(__.in('relates_to_batch').out("relates_to_reusable").id()).by(__.in("relates_to_batch").elementMap().fold()).toList()

With an isolated vertex:

g.addV('isoalted').property('property", 'abc').property('batchId', 'batch-a').property('reusableId', 'r2).iterate()

g.addV('isoalted').property('property", 'abc').property('batchId', 'batch-a').property('reusableId', 'r2).iterate()

Querying in this way produces the same result:

g.V().hasLabel('isolated').has('batchId', 'batch-a').elementMap().toList()

g.V().hasLabel('isolated').has('batchId', 'batch-a').elementMap().toList()

Please let me know if this doesn't make sense

Solution

We're basically talking about denormalization here. denormalization is common for graphs as it is for relational data structures and it comes with the same drawbacks. Is this a case for denormalization? Based on this simple example, I'd say "no" because you really just have a single hop or so to collect what you need and you're done. But, I also don't know any other statistics about your data structure and other expected query patterns so it's hard to say with certainty that you shouldn't denormalize.

That said, if denormalization is the answer, do you denormalize to a wholly disconnected vertex? i still don't think i'd recommend that based on what i know. You're most painful traversal is a two hop of

__.in('relates_to_batch').out("related_to_reusable")

__.in('relates_to_batch').out("related_to_reusable")

to get an

id

id

or perhaps multiple ids. Considering adding a property of "reusableIds" to "batch-a" and store a

List

List

of the ids there (or use multi-properties, https://tinkerpop.apache.org/docs/current/reference/#vertex-properties).

That seems like the most natural model to me since "isolated" is really just a "batch" with properties containing various things its connected to. Seems better to me to not introduce an "isolated" concept for that and denormalize to a thing that is actually part of your graph and connected.

g.V().hasLabel('batch').has('batchId', 'batch-a').elementMap().toList()

g.V().hasLabel('batch').has('batchId', 'batch-a').elementMap().toList()

I'm still hesitant to say denormalize at all though. I suppose you can do it for ease of querying sake, but it's more often done for performance reasons. I also could be missing more context with this advice, but I think i'll stick with what I've posted here as an answer. gremlin

Jump to solution

Isolated vertices vs connected vertices with no join benefit

g.addV('batch').property(id,'batch-a').as('a').
  addV('batch').property(id,'batch-b')as('b').
  addV('reusable').property(id, 123).as('r1').
  addV('reusable').property(id, 123).as('r2').
  addE('link').from('a').to('r').
  addE('link').from('b').to('r2').iterate()

g.addV('batch').property(id,'batch-a').as('a').
  addV('batch').property(id,'batch-b')as('b').
  addV('reusable').property(id, 123).as('r1').
  addV('reusable').property(id, 123).as('r2').
  addE('link').from('a').to('r').
  addE('link').from('b').to('r2').iterate()

g.addV('connected').property('property", 'abc').as('coonected-v).addE('relates_to_batch').from('connected-a).to('batch-a').addE('related_to_reusable').from('connected-a').to('r1).iterate()

g.addV('connected').property('property", 'abc').as('coonected-v).addE('relates_to_batch').from('connected-a).to('batch-a').addE('related_to_reusable').from('connected-a').to('r1).iterate()

Querying this looks like:

g.V('batch-a').project('batchId', 'reusableId', 'connected').by(T.id).by(__.in('relates_to_batch').out("relates_to_reusable").id()).by(__.in("relates_to_batch").elementMap().fold()).toList()

g.V('batch-a').project('batchId', 'reusableId', 'connected').by(T.id).by(__.in('relates_to_batch').out("relates_to_reusable").id()).by(__.in("relates_to_batch").elementMap().fold()).toList()

With an isolated vertex:

g.addV('isoalted').property('property", 'abc').property('batchId', 'batch-a').property('reusableId', 'r2).iterate()

g.addV('isoalted').property('property", 'abc').property('batchId', 'batch-a').property('reusableId', 'r2).iterate()

Querying in this way produces the same result:

g.V().hasLabel('isolated').has('batchId', 'batch-a').elementMap().toList()

g.V().hasLabel('isolated').has('batchId', 'batch-a').elementMap().toList()

Please let me know if this doesn't make sense

Solution

__.in('relates_to_batch').out("related_to_reusable")

__.in('relates_to_batch').out("related_to_reusable")

to get an

id

id

or perhaps multiple ids. Considering adding a property of "reusableIds" to "batch-a" and store a

List

List

g.V().hasLabel('batch').has('batchId', 'batch-a').elementMap().toList()

g.V().hasLabel('batch').has('batchId', 'batch-a').elementMap().toList()

Jump to solution

Isolated vertices vs connected vertices with no join benefit

Isolated vertices vs connected vertices with no join benefit

Continue the conversation

Apache TinkerPop

Similar Threads

Similar Threads

Continue the conversation

Apache TinkerPop

Similar Threads