unipop icon indicating copy to clipboard operation
unipop copied to clipboard

Published 20 hours ago • verified publisher icon unipop-graph

Cardinality Strategy

Open rmagen opened this issue 8 years ago • 0 comments

Most database optimizers use statistics-based cardinality estimates to to determine the optimal order in which to run a query's steps. Should we do something similar?

We could implement a TraversalStrategy that rearranges the Traversal's steps according to its estimated cardinality. Each Controller provide the necessary information by utilizing its database's capabilities. e.g. Oracle Statistics.

Tinkerpop has something similar in its MatchStep, except it does a run-time statistics calculation for every traversal.

  1. Should we use MatchStep's MatchAlgorithm to implement this feature?
  2. Why is this only implemented for MatchStep? Can't the same logic be applied for all steps in the traversal?

rmagen avatar May 15 '16 13:05 rmagen