You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What version of Dgraph are you using?
Docker image of v1.0.5
Have you tried reproducing the issue with latest release?
It's the latest release. Not tested with git HEAD.
What is the hardware spec (RAM, OS)?
Running in a local minikube on Fedora. I don't think that RAM matters in the current setup as there are only a couple of entries in the test DB.
Steps to reproduce the issue (command/config used to run Dgraph).
dgraph server --my=$(hostname -f):7080 --lru_mb 1024 --zero dgraph-zero-0.dgraph-zero.default.svc.cluster.local:5080
As the containerCount is 1 and the others are 0, I'd expect hasChildren to be true in case of the given query. Please correct me if this expectation is wrong for some reason I don't understand yet :-)
Using math(containerCount + userCount + deviceCount > 0) results in true - which is expected.
The text was updated successfully, but these errors were encountered:
What version of Dgraph are you using?
Docker image of v1.0.5
Have you tried reproducing the issue with latest release?
It's the latest release. Not tested with git HEAD.
What is the hardware spec (RAM, OS)?
Running in a local minikube on Fedora. I don't think that RAM matters in the current setup as there are only a couple of entries in the test DB.
Steps to reproduce the issue (command/config used to run Dgraph).
dgraph server --my=$(hostname -f):7080 --lru_mb 1024 --zero dgraph-zero-0.dgraph-zero.default.svc.cluster.local:5080
Expected behaviour and actual result.
The schema:
The contents:
The non @normalize query:
The result (stripped):
As the containerCount is 1 and the others are 0, I'd expect hasChildren to be true in case of the given query. Please correct me if this expectation is wrong for some reason I don't understand yet :-)
Using
math(containerCount + userCount + deviceCount > 0)
results intrue
- which is expected.The text was updated successfully, but these errors were encountered: