# Live loader produces duplicates with upsertPredicate enabled

**URL:** <https://discuss.dgraph.io/t/live-loader-produces-duplicates-with-upsertpredicate-enabled/15497>\
**Category:** Dgraph\
**Created:** [September 7, 2021, 12:48pm UTC](https://discuss.dgraph.io/t/live-loader-produces-duplicates-with-upsertpredicate-enabled/15497 "2021-09-07T12:48:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![martaver](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/martaver/32/8682_2.png) [@martaver](https://discuss.dgraph.io/u/martaver)\
**Post date:** [September 7, 2021, 12:48pm UTC](https://discuss.dgraph.io/t/live-loader-produces-duplicates-with-upsertpredicate-enabled/15497/1 "2021-09-07T12:48:59Z")

</div>

## Report a Dgraph Bug

I’m pushing a graphql schema to dgraph using `xid` fields on types that map to the `xid` dgraph predicate. When I run live loader with upsertPredicate ‘xid’ however, subsequent imports result in duplicate records being created.

### What version of Dgraph are you using?

> **Dgraph Version**
>
> ```auto
> $ dgraph version
>  
> Dgraph version : v21.03.2
> Dgraph codename : rocket-2
> Dgraph SHA-256 : 00a53ef6d874e376d5a53740341be9b822ef1721a4980e6e2fcb60986b3abfbf
> Commit SHA-1 : b17395d33
> Commit timestamp : 2021-08-26 01:11:38 -0700
> Branch : HEAD
> Go version : go1.16.2
> jemalloc enabled : true
> 
> ```

### Have you tried reproducing the issue with the latest release?

Yes

### What is the hardware spec (RAM, OS)?

MacOS / Docker / 16GB (8GB allocated)

### Steps to reproduce the issue (command/config used to run Dgraph).

This is the schema I’m pushing to my dgraph instance:  
[index.graphqls](https://discuss.dgraph.io/uploads/short-url/76C50lE7Iu5k02JrNKzHLlArXWo.graphqls) (2.2 KB)

This is the JSON file I’m live loading.  
[out.json](https://discuss.dgraph.io/uploads/short-url/RK9NwLViqcAk947rXZjSbvR4Jo.json) (98.7 KB)

This is the command I’m using: `dgraph live --files /path_to/out.json --upsertPredicate "xid"`

### Expected behaviour and actual result.

Buildings with the same `xid` value should not be duplicated, but they are.

---

<div class="post-metadata">

**Author:** ![martaver](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/martaver/32/8682_2.png) [@martaver](https://discuss.dgraph.io/u/martaver)\
**Post date:** [September 7, 2021, 12:49pm UTC](https://discuss.dgraph.io/t/live-loader-produces-duplicates-with-upsertpredicate-enabled/15497/2 "2021-09-07T12:49:27Z")

</div>

It’s entirely possible that I’m missing something obvious here, in that case please point me in the right direction 🙂

---

<div class="post-metadata">

**Author:** ![MichelDiz](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/micheldiz/32/11873_2.png) [@MichelDiz](https://discuss.dgraph.io/u/MichelDiz)\
**Post date:** [September 7, 2021, 2:03pm UTC](https://discuss.dgraph.io/t/live-loader-produces-duplicates-with-upsertpredicate-enabled/15497/3 "2021-09-07T14:03:03Z")

</div>

Duplicate (or rename it) the XID value in the dataset to the key “uid”. In fact, you don’t need the XID field during the live load. This field is necessary for the dataset already in the DB only. For the case you are loading new data, you have to use UID instead of XID.

The upsert feature in live load takes UID in the dataset into consideration instead of XID. And when it loads it, it creates the XID field to compare with the new data during the live load.

BTW, the UID key have to be a blank node. It will throw an error if you don’t prefix it with `_:`

---

<div class="post-metadata">

**Author:** ![MattH](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/matth/32/8007_2.png) [@MattH](https://discuss.dgraph.io/u/MattH)\
**Post date:** [March 18, 2022, 6:05pm UTC](https://discuss.dgraph.io/t/live-loader-produces-duplicates-with-upsertpredicate-enabled/15497/4 "2022-03-18T18:05:24Z")

</div>

@martaver Curious if you ever got this working? I’m encountering the same issue with Live Loader using  
a graphql schema and json formatted data.

I’m trying to follow the advice of MichelDiz above who suggested mapping the XID value to the key “uid” but not having any luck.

If you got it working, could you please post what your schema and .json file looked like?

Thanks!