Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
inconsistent result when sorted predicate does not contain value on some nodes #2672
If you suspect this could be a bug, follow the template.
index a predicate, for example: created_at @ time
then query with orderasc/desc created_at and with first: 10
result should show only nodes with created_at
actual results, 50% of times it return rows with created_at,
as stated in few last post here:
I think I've mentioned before, empty nodes will continue to exist. And they are considered Orphans / Deleted. Ignore them.
Using the deletion procedure in the documentation still does this happen?
@u007 Please can you try with a later version. Just to check. I tried reproduce with the template I did there in the Discuss, but I did not get that effect.
I need something that is obvious, or that put me on the right path to reproduce. Otherwise it is a waste of time, no one will analyze the case in the short term.
Filtering is good, but use literal predicates. Do not use
I'm not sure if you're just expressing yourself. The correct way to express a literal predicate would be
btw, About this statement:
Can you show the used Query? In practice Dgraph does not return Nodes that do not have "created_at" (before) or if you query for "created_at" with sort or filter by it. If the case is "Phantom Nodes", the use of the filter is recommended for now.
This issue here #2484 is related - As you can see, the predicate still there hided in the Phantom Node. So that's why need to filter.
Any updates let me know. I'll mark this issue to close in a week if there are no changes. Or if see srfrog/gus work on it and fix it.
Thanks all for your report and feedback!