# Upsert with multiple UIDs

**URL:** <https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223>\
**Category:** Users\
**Tags:** mutation, java-client\
**Created:** [October 12, 2019, 12:02am UTC](https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223 "2019-10-12T00:02:07Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![devinbost](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/devinbost/32/2126_2.png) [@devinbost](https://discuss.dgraph.io/u/devinbost)\
**Post date:** [October 12, 2019, 12:02am UTC](https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223/1 "2019-10-12T00:02:07Z")

</div>

Hi,

I am wanting to create an upsert that updates the data for three UIDs. When I run this query:

```auto
{
 var(func: has(products)){
  productsUid as uid
  productNode as products @filter(eq(productId, 10888870)){
    optionNode as options @filter(eq(optionId, 16818278)){
      uid
    }
  }
 }
 getVals(func: uid(productsUid)) @normalize {
  productsUid : uid
  products @filter(uid(productNode)){
    productUid : uid
  	options @filter(uid(optionNode)){
      optionUid : uid
    }
  }
 }
}

```

I get this result:

```auto
{
  "extensions": {
    "server_latency": {
      "parsing_ns": 18220,
      "processing_ns": 13088415,
      "encoding_ns": 474410
    },
    "txn": {
      "start_ts": 124254
    }
  },
  "data": {
    "getVals": [
      {
        "optionUid": "0x937",
        "productUid": "0x934",
        "productsUid": "0x930"
      }
    ]
  }
}

```

What I want to do next is create an upsert for all three of these UIDs in a way that will create the product node and option node (so the product is a child of product **s** , and the option is a child of the product) if missing. For example, I want to do something like this:

```auto
upsert {
  query {
    [insert query from above]
  }

  mutation {
    set {
      {
        {
           "uid": " **productsUid**",
           "products": [
             {
               "productId": 10888870,
               "uid": " **productUid**",
               "options": [
                 {
                   "optionId": 16818278,
                    "uid": " **optionUid**",
                   "color": "red"
                 }
               ]
             }
           ]}
       }
    }
  }
}

```

Is there a way to do this?  
I’m using the Java Client, but any upsert solution will suffice.  
A requirement for the upsert is that if a product doesn’t exist, it must create a new one under the existing products collection. Similarly, if an option doesn’t exist, it must create a new one under the existing product. If neither the product nor the option exist, then it must create them both.

---

<div class="post-metadata">

**Author:** ![amanmangal](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/amanmangal/32/1249_2.png) [@amanmangal](https://discuss.dgraph.io/u/amanmangal)\
**Post date:** [October 12, 2019, 12:11pm UTC](https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223/2 "2019-10-12T12:11:29Z")

</div>

I am not sure I understand all the details, but your above upsert [1] will probably look like as follows in GraphQL±. There could be minor differences due to how your data model is, so check once. You can also add conditions using Conditional Upsert [2].

```auto
upsert {
  query {
    [insert query from above]
  }

  mutation {
    set {
        uid(productsUid) <products> uid(productUid) .
        uid(productUid) <productId> "10888870" .
        uid(productUid) <options> uid(optionUid) .
        uid(optionUid) <color> "red" .
        uid(optionUid) <optionId> "16818278" .
    }
  }
}

```

[1] [Mutation - Dgraph](https://docs.dgraph.io/mutations/#upsert-block)  
[2] [Mutation - Dgraph](https://docs.dgraph.io/mutations/#conditional-upsert)

### Quick update

> I (@micheldiz) marked Aman’s answer as the correct one because it is in fact what corresponds to the requested. However, if you (future reader) want to continue reading below. Please note that other topics are covered below and this here is the right answer. The conversation below is more about troubleshooting than about the title.

---

<div class="post-metadata">

**Author:** ![devinbost](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/devinbost/32/2126_2.png) [@devinbost](https://discuss.dgraph.io/u/devinbost)\
**Post date:** [October 14, 2019, 3:57pm UTC](https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223/3 "2019-10-14T15:57:11Z")

</div>

This is great! Thanks for the help!

When I attempt to structure the upsert with the Java client (as per this link: [GitHub - dgraph-io/dgraph4j: Official Dgraph Java client](https://github.com/dgraph-io/dgraph4j#running-an-upsert-query--mutation)) like this:

```auto
String query = "query {\n" +
  "user as var(func: eq(email, \"wrong_email@dgraph.io\"))\n" +
  "}\n";
Mutation mu =
  Mutation.newBuilder()
  .setSetNquads(ByteString.copyFromUtf8("uid(user) <email> \"correct_email@dgraph.io\" ."))
  .build();
Request request = Request.newBuilder()
  .setQuery(query)
  .addMutations(mu)
  .setCommitNow(true)
  .build();
txn.doRequest(request);

```

I get the message that `addMutations` cannot be found. I checked the imports from the sample here: [dgraph4j/samples/DgraphJavaSample/src/main/java/App.java at master · dgraph-io/dgraph4j · GitHub](https://github.com/dgraph-io/dgraph4j/blob/master/samples/DgraphJavaSample/src/main/java/App.java)  
and my imports match. Am I using the wrong builder for the upsert?

![image](https://canada1.discourse-cdn.com/flex007/uploads/dgraph/original/2X/c/cd1c9422a20d5e05d4d98fb39d61fcdbc51854d0.png)

---

<div class="post-metadata">

**Author:** ![amanmangal](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/amanmangal/32/1249_2.png) [@amanmangal](https://discuss.dgraph.io/u/amanmangal)\
**Post date:** [October 14, 2019, 4:57pm UTC](https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223/4 "2019-10-14T16:57:49Z")

</div>

What version of Dgraph4j are you using?

---

<div class="post-metadata">

**Author:** ![devinbost](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/devinbost/32/2126_2.png) [@devinbost](https://discuss.dgraph.io/u/devinbost)\
**Post date:** [October 14, 2019, 5:31pm UTC](https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223/5 "2019-10-14T17:31:27Z")

</div>

We’re using 1.7.3.

```auto
        <dependency>
            <groupId>io.dgraph</groupId>
            <artifactId>dgraph4j</artifactId>
            <version>1.7.3</version>
        </dependency>

```

---

<div class="post-metadata">

**Author:** ![amanmangal](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/amanmangal/32/1249_2.png) [@amanmangal](https://discuss.dgraph.io/u/amanmangal)\
**Post date:** [October 14, 2019, 5:35pm UTC](https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223/6 "2019-10-14T17:35:49Z")

</div>

These changes are only available after 2.0.2 version.

---

<div class="post-metadata">

**Author:** ![devinbost](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/devinbost/32/2126_2.png) [@devinbost](https://discuss.dgraph.io/u/devinbost)\
**Post date:** [October 14, 2019, 5:49pm UTC](https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223/7 "2019-10-14T17:49:46Z")

</div>

Awesome. Thanks! Is the 2.0.2 client backward compatible with Dgraph (Zero, Alpha, and Ratel) or is it only compatible with Dgraph after a particular version?

---

<div class="post-metadata">

**Author:** ![amanmangal](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/amanmangal/32/1249_2.png) [@amanmangal](https://discuss.dgraph.io/u/amanmangal)\
**Post date:** [October 14, 2019, 6:06pm UTC](https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223/8 "2019-10-14T18:06:06Z")

</div>

2.\* of dgraph4j is only compatible with dgraph 1.1.\* (Alpha and Zero)

---

<div class="post-metadata">

**Author:** ![devinbost](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/devinbost/32/2126_2.png) [@devinbost](https://discuss.dgraph.io/u/devinbost)\
**Post date:** [October 14, 2019, 7:07pm UTC](https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223/9 "2019-10-14T19:07:44Z")

</div>

We updated the client version, and we’re attempting to execute a mutation to setup our local dgraph database for our integration tests, and we’re getting `StatusRuntimeExecution: UNKNOWN: Empty query`

Here’s our mutation code:

```auto
Transaction txn = dgraphClient.newTransaction();
DgraphProto.Mutation mu = DgraphProto.Mutation.newBuilder()
                    .setSetJson(ByteString.copyFromUtf8(message)).build();

DgraphProto.Request request = DgraphProto.Request.newBuilder()
                    .addMutations(mu)
                    .build();

Map uids = txn.doRequest(request).getUidsMap();

```

Here’s the exception detail:

```auto
[main] ERROR updates.ImInStockStatusReaderWriterTest - Showing stack trace: java.lang.RuntimeException: java.util.concurrent.CompletionException: java.lang.RuntimeException: The doRequest encountered an execution exception:
	at io.dgraph.AsyncTransaction.lambda$doRequest$2(AsyncTransaction.java:173)
	at java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:822)
	at java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:797)
	at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
	at java.util.concurrent.CompletableFuture$AsyncSupply.run$$$capture(CompletableFuture.java:1595)
	at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java)
	at java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1582)
	at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
	at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
	at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
	at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157)
Caused by: java.util.concurrent.CompletionException: java.lang.RuntimeException: The doRequest encountered an execution exception:
	at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
	at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)
	at java.util.concurrent.CompletableFuture$AsyncSupply.run$$$capture(CompletableFuture.java:1592)
	... 6 more
Caused by: java.lang.RuntimeException: The doRequest encountered an execution exception:
	at io.dgraph.DgraphAsyncClient.lambda$runWithRetries$2(DgraphAsyncClient.java:212)
	at java.util.concurrent.CompletableFuture$AsyncSupply.run$$$capture(CompletableFuture.java:1590)
	... 6 more
Caused by: java.util.concurrent.ExecutionException: io.grpc.StatusRuntimeException: UNKNOWN: Empty query
	at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
	at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)
	at io.dgraph.DgraphAsyncClient.lambda$runWithRetries$2(DgraphAsyncClient.java:180)
	... 7 more
Caused by: io.grpc.StatusRuntimeException: UNKNOWN: Empty query
	at io.grpc.Status.asRuntimeException(Status.java:533)
	at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:442)
	at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
	at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
	at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
	at io.grpc.internal.CensusStatsModule$StatsClientInterceptor$1$1.onClose(CensusStatsModule.java:700)
	at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
	at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
	at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
	at io.grpc.internal.CensusTracingModule$TracingClientInterceptor$1$1.onClose(CensusTracingModule.java:399)
	at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:507)
	at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:66)
	at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close(ClientCallImpl.java:627)
	at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$700(ClientCallImpl.java:515)
	at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:686)
	at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:675)
	at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
	at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

```

We get the same exception if we use:

```auto
DgraphProto.Response response = txn.mutate(mu);
uids = response.getUidsMap();

```

instead of:

`Map uids = txn.doRequest(request).getUidsMap();`

Before we updated the version of our Dgraph client, our working mutation code was this:

```auto
Assigned response;

Transaction txn = dgraphClient.newTransaction();
try {
     Mutation mu = Mutation.newBuilder().setSetJson(ByteString.copyFromUtf8(message)).build();
     response = txn.mutate(mu);
     txn.commit();
} finally {
     txn.discard();
}
//get uids from mutate
Map uids = response.getUidsMap();

```

What changes do we need to make to run a mutation with the new version of the Dgraph client?

---

<div class="post-metadata">

**Author:** ![amanmangal](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/amanmangal/32/1249_2.png) [@amanmangal](https://discuss.dgraph.io/u/amanmangal)\
**Post date:** [October 14, 2019, 7:19pm UTC](https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223/10 "2019-10-14T19:19:08Z")

</div>

As I said, you have to be running v1.1.0 version of dgraph. What version are you running now?

---

<div class="post-metadata">

**Author:** ![devinbost](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/devinbost/32/2126_2.png) [@devinbost](https://discuss.dgraph.io/u/devinbost)\
**Post date:** [October 14, 2019, 9:43pm UTC](https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223/11 "2019-10-14T21:43:24Z")

</div>

I hadn’t updated the docker container, so updating the docker container to v1.1.0 seemed to get me farther.  
However, when I try to run the mutate now, my mutation doesn’t seem to be reaching Dgraph. I know my hostname and port are set correctly because I’m able to run `alter` to set the schema. I get UIDs back from the mutate, but there’s no evidence that the mutation actually ran in Dgraph. The alpha and zero logs don’t show anything about the mutation, and the data doesn’t show up when I query it in Ratel. I’ve triple checked that the hostname and port are configured correctly in my test method and in Ratel.  
Any ideas?

---

<div class="post-metadata">

**Author:** ![devinbost](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/devinbost/32/2126_2.png) [@devinbost](https://discuss.dgraph.io/u/devinbost)\
**Post date:** [October 14, 2019, 10:10pm UTC](https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223/12 "2019-10-14T22:10:27Z")

</div>

For example, we’re running:

```auto
DgraphProto.Mutation mu = DgraphProto.Mutation.newBuilder().setSetJson(ByteString.copyFromUtf8(fileContents)).build();
response = txn.mutate(mu);
txn.commit();

```

with this JSON data for the `fileContents` variable:

```auto
{
    "uid": "_:products",
  "collectionId": 1,
    "products": [
      {
        "uid": "_:product",
        "productId": 19610626,
        "options": [
          {
            "uid": "_:option",
            "optionId": 32661491,
            "color": "red"
          }
        ]
      }
    ]
}

```

---

<div class="post-metadata">

**Author:** ![amanmangal](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/amanmangal/32/1249_2.png) [@amanmangal](https://discuss.dgraph.io/u/amanmangal)\
**Post date:** [October 15, 2019, 1:06am UTC](https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223/13 "2019-10-15T01:06:22Z")

</div>

What’s the query you are running to verify whether data exists or not?

---

<div class="post-metadata">

**Author:** ![devinbost](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/devinbost/32/2126_2.png) [@devinbost](https://discuss.dgraph.io/u/devinbost)\
**Post date:** [October 15, 2019, 1:55am UTC](https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223/14 "2019-10-15T01:55:58Z")

</div>

I’ve tried several.  
Here are some of the queries we’ve tried:

```auto
{
  data(func: has(productId)) {
    _predicate_
  }
}

```

```auto
{
  data(func: has(products)) {
    _predicate_
  }
}

```

```auto
{
  data(func: has(product)) {
    _predicate_
  }
}

```

Interestingly, when I ran:

```auto
{
  data(func: has(productId)) {
    productId
  }
}

```

I actually got a productId value back:

```auto
{
  "data": {
    "data": [
      {
        "productId": 19610626
      }
    ]
  },
  "extensions": {
    "server_latency": {
      "parsing_ns": 39200,
      "processing_ns": 2303100,
      "encoding_ns": 14300,
      "assign_timestamp_ns": 1451600
    },
    "txn": {
      "start_ts": 76
    }
  }
}

```

Does the `_predicate_` statement still work?

---

<div class="post-metadata">

**Author:** ![devinbost](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/devinbost/32/2126_2.png) [@devinbost](https://discuss.dgraph.io/u/devinbost)\
**Post date:** [October 15, 2019, 2:08am UTC](https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223/15 "2019-10-15T02:08:43Z")

</div>

I was able to get more data to load by trying this:

```auto
Transaction txn = dgraphClient.newTransaction();
Map uids;
DgraphProto.Mutation mu = DgraphProto.Mutation.newBuilder()
        .setSetJson(ByteString.copyFromUtf8(message)).build();

DgraphProto.Request request = DgraphProto.Request.newBuilder()
        .addMutations(mu)
        .build();
uids = txn.doRequest(request).getUidsMap();
DgraphProto.Response response = txn.mutate(mu);
uids = response.getUidsMap();
txn.commit();

```

I’m able to get it to show up here:

 ![image](https://canada1.discourse-cdn.com/flex007/uploads/dgraph/original/2X/d/d72f2ce227fb335ecaf0f66d3ede80753ae04262.png)

However, when I query it, I still don’t get anything useful. For example:

```auto
{
  data(func: has(products)) {
    _predicate_
  }
}

```

gives me:

```auto
{
  "data": {
    "data": []
  },
  "extensions": {
    "server_latency": {
      "parsing_ns": 53700,
      "processing_ns": 3191600,
      "encoding_ns": 17700,
      "assign_timestamp_ns": 2149000
    },
    "txn": {
      "start_ts": 176
    }
  }
}

```

---

<div class="post-metadata">

**Author:** ![amanmangal](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/amanmangal/32/1249_2.png) [@amanmangal](https://discuss.dgraph.io/u/amanmangal)\
**Post date:** [October 15, 2019, 2:35am UTC](https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223/16 "2019-10-15T02:35:54Z")

</div>

(Edited after Daniel’s comment below) 1.1 version of dgraph doesn’t support \_ predicate\_.

---

<div class="post-metadata">

**Author:** ![dmai](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/dmai/32/1254_2.png) [@dmai](https://discuss.dgraph.io/u/dmai)\
**Post date:** [October 15, 2019, 3:09am UTC](https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223/17 "2019-10-15T03:09:28Z")

</div>

> [@amanmangal](#):
>
> Requires type for `has` queries to work.

This is not true. `has()` function is not related to type system. You’d need to specify the predicates you want to return in the response. Or, if you use the [type system](https://docs.dgraph.io/query-language/#type-system), then you can use `expand(_all_)` to fetch the predicates defined in the type.

---

<div class="post-metadata">

**Author:** ![devinbost](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/devinbost/32/2126_2.png) [@devinbost](https://discuss.dgraph.io/u/devinbost)\
**Post date:** [October 15, 2019, 10:11am UTC](https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223/18 "2019-10-15T10:11:21Z")

</div>

Thanks for the help. I was able to get data back by specifying the predicates in the response, like this:

```auto
{
  data(func: has(products)) {
    products{
    	productId
      options{
        optionId
      }
    }
  }
}

```

However, we relied a lot on using `_predicate_`, and I’m not sure that I understand how to use `expand(_all_)`. I tried:

```auto
{
  data(func: has(products)) {
    expand(_all_)
  }
}

```

but I get no data back. Am I missing something?  
For what it’s worth, I also tried querying based on the type, like this:

```auto
{
  data(func: type(string)) {
    expand(_all_)
  }
}

```

but I got no data back that time either.

Regarding the type system, what exactly does that mean? Am I required to provide type information as well when I create the schema? If so, how do we do that? I’m not finding any examples on the website or in the docs for the Go or Java clients.

---

<div class="post-metadata">

**Author:** ![amanmangal](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/amanmangal/32/1249_2.png) [@amanmangal](https://discuss.dgraph.io/u/amanmangal)\
**Post date:** [October 15, 2019, 7:00pm UTC](https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223/19 "2019-10-15T19:00:22Z")

</div>

> [@devinbost](#):
>
> However, we relied a lot on using `_predicate_` ,

This is something we miss too. We are considering getting this back [IMPORTANT: new behavior for expand, deprecation of \_forward\_ and \_reverse\_](http://discuss.hypermode.com/t/important-new-behavior-for-expand-deprecation-of-forward-and-reverse/5186).

Consider adding the following to the schema and then try `expand(_all_)`:

```auto
type Product {
  productId: string
  options: [Option]
}

type Option {
  optionId: string
  color: string
}

```

You will also have attach these types to corresponding nodes. For example, you upsert should look like this now -

```auto
        uid(productsUid) <products> uid(productUid) .
        uid(productsUid) <dgraph.type> "Product" .
        uid(productUid) <productId> "10888870" .
        uid(productUid) <options> uid(optionUid) .
        uid(optionUid) <dgraph.type> "Option" .
        uid(optionUid) <color> "red" .
        uid(optionUid) <optionId> "16818278" .

```

Once you add these types and attach them to nodes, `expand(_all_)` should work. You can read more about type system here [Get started with Dgraph](https://docs.dgraph.io/query-language/#type-system).

---

<div class="post-metadata">

**Author:** ![devinbost](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/devinbost/32/2126_2.png) [@devinbost](https://discuss.dgraph.io/u/devinbost)\
**Post date:** [October 15, 2019, 9:12pm UTC](https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223/20 "2019-10-15T21:12:21Z")

</div>

I added the type information to the schema, and you can see it here:

 ![image](https://canada1.discourse-cdn.com/flex007/uploads/dgraph/original/2X/0/0dc497cadfd4347cfeff7e19aaff8b021656ba37.png)

[Next page](https://discuss.dgraph.io/t/upsert-with-multiple-uids/5223.md?page=2)