Slow query times for has() function (on play.dgraph.io)

Issues Dgraph
, , ,
7

Nope, the dataset was updated. This query will work.

{
  films(func: type(Film), first:100){
    name@en
    dgraph.type
  }
}

The problem with your query is that you are asking for “name”, but the dataset has language support. When it has language support in general you have to search in the pair lang you want.

BTW, avoid doing “benchmark” tests over the play website. It has a simple cluster. It is not made for this. If you force it with a heavy query, the service may crash and take time to come back. It was meant for simple exploration.

As the predicate “name” exists, the DB assumes you know that there is some data somewhere. So it will scan over the DB cuz you asked for it. But the problem is that there’s no data over “name” as I mentioned before it has language support.

1 Like