Question about edges / relationships

Users
1

Is there any way to get the information of the connection between two nodes in the JSON response ?

{
  addresses(func: eq(address, ["000F5D2f"], ["00514912"])) {
    address

    containerItems0: ~box0 {
      address
      box1 {
        address
      }
        box0 {
        address
      }
    }

    containerItems1: ~box1 {
      address
      box0 {
        address
      }
        box1 {
        address
      }
    }
}
}

This gets the containerItems connected to the box0 and box1 of the result by a reverse predicate.
This works well, but in ratle, I can see the cross-connections between the boxes from the first and the second address through their respective containers. Meaning that if both addresses have containers that have either box0 or box1, you can see these interconnected in rattle.

When I hover over an edge that connects one container from one address to one container from the other address via a box, I can see this : 0x95b07e box1 0x95b056.

Now, my question is … is there any way to extract on the query result, these edge connections by their UID just as i see in Ratle ? The JSON output does not include the edge cross-connections or interconnected nodes. This is one of my needs in this application, but I can’t figure out how to do it. Just need to know if this is possible or needs to be done outside of dgraph.

Thanks

2

Could you clarify the element you see in Ratel with a screen shot?
Ratel UI displays the data from the JSON response so, if you see it, it should be in the JSON.
One thing Ratel is forcing is to inject the uid predicate.

So you may just have to request the uid in your query for each node:

{
  addresses(func: eq(address, ["000F5D2f"], ["00514912"])) {
    uid
    address

    containerItems0: ~box0 {
      uid
      address
      box1 {
        uid
        address
      }
     ...

There are no relationship id in Dgraph.
The relationship is in fact a triple. Like the one you mentioned
0x95b07e box1 0x95b056
This identifies the relationship between 2 nodes using the predicate box1.

In this example could you clarify the type of the node 0x95b07e and the type of the node 0x95b07e?

Note: querying the RDF (the triples) could help you analyze the data.
You can do that with /query?respFormat=rdf in HTTP or specifically requesting RDF format in the client library.