Bugs or missuse - Attaching new node from previous query var uid

[RafaARV (Rafael Arturo Rocha Vidaurri)]

I have this schema:

mutation {
  schema {
    graph: string @index(exact,term) .
    dummy_param: string @index(exact,term) .
    edge: uid @count .
    name: string @index(exact,term) .
  }
}

Then I create a root node:

mutation {
  set {
    _:root <graph> "graph1" .
    _:root <entry_point> "graph1" .
    _:root <name> "root" .
  }
}

Then I try to add a node to the root node by running:

{
  root as var(func:eq(name, "root"))@filter(eq(graph, "graph1")) {}
}
mutation {
   set {
    uid(root) <edge> _:node .
    _:node <name> "node1" .
    _:node <graph> "graph1" .
  }
}

But if I query like this:

{
  recurse(func:eq(name, "root")){
    name
    graph
    edge
  }
}

I get what I put as “first” in the attached image.
Shouldn’t the result be more like what I put as “second” in the attached image?

[pawan (Pawan Rawal)]

mutation {
set {
_:root <graph_name> “graph1” .
_:root <entry_point> “graph1” .
_:root <name> “root” .
}
}

I think the first mutation in the example above should be should be

_:root <graph> "graph1" .

Irrespective of that, this is a bug with the recurse feature.

[RafaARV (Rafael Arturo Rocha Vidaurri)]

Thank you Pawan.

Yes, I had a mistake in “graph_name” it is “graph” . Despite of that the bug remains.
But to be honest it doesn’t seems to be a “recurse error”, the thing is that I found a work around by repeating the first func filter in the “@filter” section. So, if I add a node like this:

{
  root as var(func:eq(name, "root"))@filter(eq(graph,"graph1") and eq(name,"root"))
}

mutation{
  set{
    uid(root) <link> _:node .
    _:node <name> "node1" .
    _:node <graph> "graph1" .
  }
}

The extra loop in the new node goes away and also any other extra link that used to appear using the past query (it used to return all the nodes in “graph1” instead of returning only the one with the “root” name, like if it was ignoring the first “func filter”).

[pawan (Pawan Rawal)]

But to be honest it doesn’t seems to be a “recurse error”,

You are right, it’s not a bug with recurse and you are right again about filter overriding the root function. There is a issue for this https://github.com/dgraph-io/dgraph/issues/1455 a fix for which will be merged today and will be part of the next release.