The new collect() translation is more flexible and allows to define iterator variables. However, the gather/scatter pattern may be quite heavy, especially if the query contains several nested collects.
Need to perform some benchmarking to see if there is a translation better than the other. If it is the case it would be possible to have two kinds of translations: a simple one (outE/inV) if the collect iterator is never accessed, and a complex one (gather/scatter or similar) if the iterator is used in a nested operation.
This question comes from the discussion with @bluezio about Mogwaï performance compared to Hawk/Neo4j and Hawk/OrientDB
The new collect() translation is more flexible and allows to define iterator variables. However, the gather/scatter pattern may be quite heavy, especially if the query contains several nested collects.
Need to perform some benchmarking to see if there is a translation better than the other. If it is the case it would be possible to have two kinds of translations: a simple one (outE/inV) if the collect iterator is never accessed, and a complex one (gather/scatter or similar) if the iterator is used in a nested operation.
This question comes from the discussion with @bluezio about Mogwaï performance compared to Hawk/Neo4j and Hawk/OrientDB