i found it doesn’t work. i tried: schema: “name:string @index (hash) @upsert .\n” mutate data like { set { _:p1 <name> "p1" . _:p2 <name> "p2" . } } and then mutate then same: { set { _:p1 <name> "p1" . _:p2 <name> "p2" . } } it cannot detect the conflicts of n…

@upsert directive is important to detect conflicts

shanghai-Jerry (Jerry You) June 29, 2018, 3:49am 7

i am not using docker

Dgraph v1.0.6 is out

Topic		Replies	Views
When to use the upsert directive Users	3	1870	November 1, 2018
Upsert Will duplicate nodes be generated in the process of multithreading data update using the upsert block Dgraph	9	592	March 13, 2021
Something wrong with upsert Dgraph kind:question , area:querylang	4	736	November 23, 2020
Upsert not working as expected Users kind:question , dgraph	3	490	November 14, 2020
@upset directive doesn't ensure uniqueness Dgraph mutation , kind:bug	3	538	October 30, 2019