Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Don't try to store 7 million items in a Neo4j property -- you're right, that's wrong.</p> <p>Redis and Neo4j often make a good pairing, but I don't quite understand what you're trying to do or what you mean in "d" -- what are the key/value pairs, and how do they relate to the nodes and relationships in the graph? Examples would help.</p> <p>UPDATE: The most natural way to do this with a graph database is to store it as a property on the edge between the two nodes. Then you can use Gremlin to get its value.</p> <p>For example, to return a property on an edge that exists between two vertices (nodes) that have some properties:</p> <pre><code>start = g.idx('vertices')[[key:value]] // start vertex edge = start.outE(label).as('e') // edge end = edge.inV.filter{it.someprop == somevalue} // end vertex prop = end.back('e').prop // edge property return prop </code></pre> <p>You could store it in an index like you suggested, but this adds more complexity to your system, and if you need to reference the data as part of the traversal, then you will either have to store duplicate data or look it up in Redis during the traversal, which you can do, see:</p> <p>Have Gremlin Talk to Redis in Real Time while It's Walking the Graph <a href="https://groups.google.com/d/msg/gremlin-users/xhqP-0wIg5s/bxkNEh9jSw4J" rel="nofollow">https://groups.google.com/d/msg/gremlin-users/xhqP-0wIg5s/bxkNEh9jSw4J</a></p> <p>UPDATE 2: </p> <p>If the ID of vertex <code>a</code> and <code>b</code> are known ahead of time, then it's even easier: </p> <pre><code>g.v(a).outE(label).filter{it.inVertex.id == b}.prop </code></pre> <p>If vertex <code>a</code> and <code>b</code> are known ahead of time, then it's: </p> <pre><code>a.outE(label).filter{it.inVertex == b}.prop </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PONeo4j Key-Value List recommended implementation
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USespeed
    1. USespeed
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PONeo4j Key-Value List recommended implementation
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWe have Node A and Node B and have a relationship between between Node A and B. This is a given.
      singulars
      1. PO
      1. USOrlok_Assassin
    2. COSee additions to question
      singulars
      1. PO
      1. USOrlok_Assassin
    3. COThat's what I originally had but backed away from that, because, how to find the edge between two nodes quickly. If Node A is the starting point and has an edge with Node B and another with Node C, but the start/end nodes of the traversal are known ahead of time, i,e, from A to B, How to get that edge without it looking at the edge between Node A to C. Meaning the only way to do this is start at A, get all relationships of a type, see who the end node is for each edge, until it matches B. If A has edges with many other nodes this could be expensive. Or am I missing something?
      singulars
      1. PO
      1. USOrlok_Assassin
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload