Moved from GitHub dgraph/5770
Posted by danielmai:
What version of Dgraph are you using?
v20.03.3
Have you tried reproducing the issue with the latest release?
Yes
What is the hardware spec (RAM, OS)?
Ubuntu Linux, Docker
Steps to reproduce the issue (command/config used to run Dgraph).
-
Run Dgraph cluster
-
Set the following schema with a string predicate:
curl 'localhost:8080/alter' \ -d 'name: string .'
-
Run the following mutation
curl 'localhost:8080/mutate?commitNow=true' \ -H "Content-Type: application/json" \ -d '{"set":[{"uid":"_:root","connects":[{"name": "A"},{"name":"B"}]}]}'
-
Run the following query
curl 'localhost:8080/query' \ -H "Content-Type: application/graphql+-" \ -d ' { var(func: has(name)) { n as name } names(func: uid(n)) { name } nameA(func: eq(val(n), "A")) { name } nameB(func: eq(val(n), "B")) { name } q(func: eq(val(n), ["A", "B"])) { name } }'
Expected behaviour and actual result.
The actual query result is:
{
"data": {
"q": [
{
"name": "A"
}
]
}
}
The expected query result is that eq(val(n), ["A", "B"])
in the filter returns back both nodes A and B in the response:
{
"data": {
"q": [
{
"name": "A"
},
{
"name": "B"
}
]
}
}
When running a query to get the individual blocks out, I see the queries for individual matches to return back the data as expected:
Query
curl 'localhost:8080/query' \
-H "Content-Type: application/graphql+-" \
-d '
{
var(func: has(name)) {
n as name
}
names(func: uid(n)) {
name
}
nameA(func: eq(val(n), "A")) {
name
}
nameB(func: eq(val(n), "B")) {
name
}
q(func: eq(val(n), ["A", "B"])) {
name
}
}'
Response
{
"data": {
"names": [
{
"name": "A"
},
{
"name": "B"
}
],
"nameA": [
{
"name": "A"
}
],
"nameB": [
{
"name": "B"
}
],
"q": [
{
"name": "A"
}
]
}
}