Optimize binding of multiple columns in transitive paths#2844
Draft
schaetzr wants to merge 2 commits intoad-freiburg:masterfrom
Draft
Optimize binding of multiple columns in transitive paths#2844schaetzr wants to merge 2 commits intoad-freiburg:masterfrom
schaetzr wants to merge 2 commits intoad-freiburg:masterfrom
Conversation
Contributor
Author
|
In the first attempt, I tried to make the This happens on my toy example dataset: with the query SELECT * WHERE {
VALUES (?s ?o) {(<Q1> <Q2>)} .
?s <P1>* ?o
}i am working on finding out what mistake I made and how to fix the error |
Overview
Conformance check failed ❌Test Status Changes 📊
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



This PR aims to improve query planning for special queries where both sides of a triple are already bound (= are variables that have values already assigned to them). Currently, this would invoke a scan over the whole dataset and then execute a multi-column join instead of picking one column as start node and thereby vastly improving query runtime.
Example:
... creates a multicolumn join, but it'd be better if it ran like:
which instead calls a transitive path operation in the query planer.
This PR is WIP and currently, nothing regarding this optimization is working as expected. Tests should also fail.