-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Closed as not planned
Closed as not planned
Copy link
Labels
Stalearea/querylangIssues related to the query language specification and implementation.Issues related to the query language specification and implementation.dgraphIssue or PR created by an internal Dgraph contributor.Issue or PR created by an internal Dgraph contributor.kind/bugSomething is broken.Something is broken.
Description
What version of Dgraph are you using?
22.0.1
Tell us a little more about your go-environment?
No response
Have you tried reproducing the issue with the latest release?
None
What is the hardware spec (RAM, CPU, OS)?
What steps will reproduce the bug?
Expected behavior and actual result.
https://dgraph.io/docs/query-language/expand-predicates/#filtering-during-expand expand supports type filters.
using predicate "in" with @reverse.
you can declare the predicate "~in" in a type.
expand(all) will work : it will follow all the relationships declared in the node type, so it will follow ~in if present.
in our case the ~in relationship goes to a node of type "N5803".
If we expand(all) @filter(type(N5803)) , the query does not follow the ~in relationship. See the postman test with other options working.
Additional information
No response
Metadata
Metadata
Assignees
Labels
Stalearea/querylangIssues related to the query language specification and implementation.Issues related to the query language specification and implementation.dgraphIssue or PR created by an internal Dgraph contributor.Issue or PR created by an internal Dgraph contributor.kind/bugSomething is broken.Something is broken.