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
The extension to (b) comes from the fact that we tend to cover all of the query edges and vertices blindly regardless of what the query actually requests. The two plans should actually be:
In other cases, where we don’t actually need any properties all together, we should simply get the size from the Lists header and therefore not pin/unpin unnecessarily. The query:
MATCH (a)-e1->(b)
RETURN count(*);
Should generate:
P1: Scan(a) → GetListSize(e1) → GROUP BY (COUNT(*))
P1: Scan(b) → GetListSize(e1) → GROUP BY (COUNT(*))
We need to be more aware of the actual properties needed. ID is just another property we do a join on.
The text was updated successfully, but these errors were encountered:
Consider the following query:
MATCH (a)-e1->(b)
RETURN e1.time;
Currently, we consider two possible QVOs [a, b] and therefore generate two plans:
OR
The extension to (b) comes from the fact that we tend to cover all of the query edges and vertices blindly regardless of what the query actually requests. The two plans should actually be:
OR
In other cases, where we don’t actually need any properties all together, we should simply get the size from the Lists header and therefore not pin/unpin unnecessarily. The query:
MATCH (a)-e1->(b)
RETURN count(*);
Should generate:
We need to be more aware of the actual properties needed. ID is just another property we do a join on.
The text was updated successfully, but these errors were encountered: