What version of Dgraph are you using?
master (0259f3d)
I suspect this bug got introduced in #3970.
Have you tried reproducing the issue with the latest release?
does not happen in v1.1.0.
What is the hardware spec (RAM, OS)?
Ubuntu Linux 64 GB
Steps to reproduce the issue (command/config used to run Dgraph).
- Run Dgraph cluster with latest master
- Load 21-million movie data set
- Run a query with
has() with first limit for a language string predicate name@en:
{
q(func: has(name@en), first: 10) {
count(uid)
}
}
The query response returns {"count": 7}. If I set first: 100, I get {"count": 96}.
Expected behaviour and actual result.
Since there are >100 name@en edges, I expected the paginated result with first: 10 to return 10 nodes and first: 100 to return 100 nodes.
What version of Dgraph are you using?
master (0259f3d)
I suspect this bug got introduced in #3970.
Have you tried reproducing the issue with the latest release?
does not happen in v1.1.0.
What is the hardware spec (RAM, OS)?
Ubuntu Linux 64 GB
Steps to reproduce the issue (command/config used to run Dgraph).
has()withfirstlimit for a language string predicatename@en:The query response returns
{"count": 7}. If I setfirst: 100, I get{"count": 96}.Expected behaviour and actual result.
Since there are >100
name@enedges, I expected the paginated result withfirst: 10to return 10 nodes andfirst: 100to return 100 nodes.