We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
max_edge_returned_per_vertex with WHERE filtering
Why max_edge_returned_per_vertex is the absolute limit for edges per vertex, and doesn't take into concern filtering with the where clause?
I was expecting that it is a limit for edges returned, not edges existing for a vertex.
g.c.
The text was updated successfully, but these errors were encountered:
I think the truncation of max_edge_returned_per_vertex to be done after the filter when there is makes a lot of sense on the storage side.
max_edge_returned_per_vertex
@critical27 @MuYiYong what do you think, please?
Sorry, something went wrong.
MuYiYong
No branches or pull requests
max_edge_returned_per_vertex with WHERE filtering
Why max_edge_returned_per_vertex is the absolute limit for edges per vertex,
and doesn't take into concern filtering with the where clause?
I was expecting that it is a limit for edges returned, not edges existing for a vertex.
g.c.
The text was updated successfully, but these errors were encountered: