I am using graph v1.1.1 and got a weird behavior. Switching the order of the func and @filter providers different results query(func: eq(a, "true")) @filter(eq(b, "b")) {} Gives 0 matches. query(func: eq(b, "b")) @filter(eq(a, "true")) {} Gives the expected 2 matches. Maybe this is the cause ?

Switching the order of the `func` and `@filter` provides different results (v1.1.1)

Pepo (Uprtcl Team) June 10, 2020, 7:03pm 2

Heads up, this also happened to me with v20.03.0. Now working with v20.03.3, hopefully it wont happen.

Upgrade to 1.2.X or 20.0.X?

Topic		Replies	Views
Regression: v21.03 crashes on query with orderdesc Dgraph dgraph , status:accepted , kind:bug , ticket:created	12	938	June 15, 2021
Dgraph filters with eq() lt() or gt() stop working after a while for string, bool and int predicates Dgraph kind:bug	11	1392	May 30, 2020
Unconsistent @filter behaviour 1.2.0 Dgraph	7	467	February 1, 2020
Potential bug with filters when func is too long? Dgraph	1	474	December 7, 2020
Query based on eq() stopped working for one predicate Dgraph	25	1538	February 18, 2020