Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce hash join operator as alternative to bound joins #13

Open
aschwarte10 opened this issue Mar 21, 2019 · 0 comments
Open

Introduce hash join operator as alternative to bound joins #13

aschwarte10 opened this issue Mar 21, 2019 · 0 comments
Assignees
Milestone

Comments

@aschwarte10
Copy link
Contributor

In certain use situations bound joins (or generally any nested loop evaluation) might not be the optimal evaluation algorithm.

Consider the following example:

?city a :City .
?city :inRegion :BW .

There might be a large number of cities in the database, which would cause a large intermediate result set as input to the nested loop join.

If there are factors like latency involved, it might make sense to fetch the result sets of both graph patterns individually, and perform a hash join locally.

This issue is about adding the appropriate operator.

It is yet to be decided how and in which cases to activate it.

@aschwarte10 aschwarte10 self-assigned this Mar 21, 2019
@aschwarte10 aschwarte10 added this to the 6.0.0 milestone Mar 21, 2019
aschwarte10 pushed a commit that referenced this issue Apr 16, 2019
For simple queries consisting of a single BGP, we now push LIMIT clauses
into the BGP for early evaluation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant