Have you tried reproducing the issue with the latest release?
What is the hardware spec (RAM, OS)?
Steps to reproduce the issue (command/config used to run Dgraph).
Expected behaviour and actual result.
Experience Report for Feature Request
Note: Feature requests are judged based on user experience and modeled on Go Experience Reports. These reports should focus on the problems: they should not focus on and need not propose solutions.
Note: @cascade also works but may not be the most optimal (assuming performance is of concern). This is because @cascade is applied after the query: Cascade Directive - Query language