Clarification on using RDF with a Dgraph GraphQL Schema

[amaster507 (Anthony Master)]

1. Map the data to the correct predicates. See:

GraphQL vs DQL - Dgraph Blog

2. Manually create inverse edges. See:

Reverse Edge not Working as expected

What you are seeing is a data entry problem. In the GraphQL API when you add data on the predicate with an hasInverse directive on either side, the mutation rewriter in Dgraph writes this data inversely to both predicates, but when you mutate data outside of the GraphQL API endpoint such as you did with the mutate endpoint using DQL, then you bypass this control. You could have fixed this by either correcting the inverse relationships or by correctly handing inverse edges manually when using DQL…

3. Depending on how you load your data, blank nodes may not refer to the same node between loads. See:

Bulk loader same blank nodes from different rdf files

I am trying to create a user’s behavior graph and I have lots of rdf files. To make it successful, I have already created blank node for each user. like <_:user123> <ctr_id> "user123" . The problem is, <_:user123> may occur in other files(because I stored data by date): given <_:user123> <ctr_id> "user123" . in file 1, <_:user123> <gender> "male" . in file 2, <_:user123> <click> <_:banner 1> . in file 3… So, I wanna ask how can I make sure graph can merge those same blank nodes as one. I…