This CostModel uses CPU cycles to calculate the cost of physical operators.

The DynamicProgrammingPlanner uses the DPsize algorithm for inspiration.

Cardinality estimation interface.

The DynamicProgrammingPlanner uses the DPsize algorithm for inspiration.

Data class for our Edge model.

This class maps edge labels to ids and stores them in a hashmap.

Merge two given physical plans by enumerating the applicable physical operators.

Utility to import graphs generated by gMark into the kpathindex.

Hash-join physical operator.

Physical operator to lookup paths in the kPathIndex.

Extend the path index to a higher k-value.

KPathIndex interface defining the public methods of a path index.

InMemory implementation of the KPathIndex.

Log messages with the following five levels: debug, info, warning, error and fatal.

Data-structure to represent the given user input, and physical plans.

Abstract the subtreesOfSize functionality into its own class.

Flatten ParseTrees into multi-trees.

Class to print a LogicalPlan.

Nested-loop-join.

Data class for our node model.

Open hash-join to maintain compatibility with concatenating streams instead of evaluating physical plans.

The Path model contains a list of edges, as well as a list of nodes to represent a specific path.

Convert our data classes from and to the ones from com.pathdb.

Singleton class which stores the mapping from a list of edges to IDs.

This model is used for defining a search-query.

Data class for holding streams of paths where we abstract away the materializing into the MemoryManager.

Interface for physical operators.

Representation of the physical plan.

Query model which is responsible for the-life-of-a-query.

Parse the RPQ ANTLR4 AST into our internal LogicalPlan model.

The SimpleEnumerator will enumerate all physical operators we support for a given logical operator.

Evaluate a physical-plan in order to get results from the path-index.

Let all results flow through this memory manager so we have control over the data and caching.

Sort-merge-join.

Recommend using with StreamSupport.stream(iteratorStream, false);

Parse the query language into our internal representation, i.e. a LogicalPlan.

RPQ query language.

The synopsis is a statistics store to use with cardinality estimation for concatenations.

Cardinality estimation using a synopsis.

Union physical operator.