Improvement Request: Let EXISTS() on patterns use getDegree(), if able

[InverseFalcon]

This requests an improvement to EXISTS(). Current EXISTS() performs expansion to verify if the pattern exists or not.

However, when run on certain patterns, EXISTS() should be able to optimize execution by checking the degree of a relationship.

For example:

PROFILE MATCH (p:Person{name:'Keanu Reeves'})
RETURN p, EXISTS((p)-[:ACTED_IN]->()) as actor

is more expensive than this:

PROFILE MATCH (p:Person{name:'Keanu Reeves'})
RETURN p, SIZE((p)-[:ACTED_IN]->()) <> 0 as actor

yet it's exactly the same kind of query. If EXISTS() can be optimized to take advantage of situations like these where a degree check could be performed instead, it would be a nice quality of life improvement.

[InverseFalcon]

It would also be great if the same kind of enhancement could be made on WHERE <pattern> clauses too.

[InverseFalcon]

Noting that 3.2.0 addresses this request, though the WHERE clause with just the pattern and not using EXISTS still doesn't use the relationship degree.

Closing since the EXISTS optimization has been addressed.