Rewrite single chain joins to scan on materialized view if possible#2649
Rewrite single chain joins to scan on materialized view if possible#2649ullingerc wants to merge 84 commits intoad-freiburg:masterfrom
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #2649 +/- ##
==========================================
- Coverage 91.60% 91.56% -0.05%
==========================================
Files 483 489 +6
Lines 41360 41626 +266
Branches 5493 5549 +56
==========================================
+ Hits 37886 38113 +227
- Misses 1897 1913 +16
- Partials 1577 1600 +23 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
joka921
left a comment
There was a problem hiding this comment.
A first round, but unfortunately only for the stuff in parser and util.
For the sake of progress, I would suggest splitting these + their unit tests to a separate PR, s.t. we can make this one smaller, and get incremental progress.
| // NOTE: This does not guarantee completeness, so it might return `false` even | ||
| // though we could be invariant to a `GraphPatternOperation`. | ||
| struct BasicGraphPatternsInvariantTo { |
There was a problem hiding this comment.
I understand now, but really can't parse the name still, maybe we come up with something... :)
Overview
Conformance check passed ✅No test result changes. |
|



This change introduces the first part of infrastructure for rewriting joins to scans on materialized views. Additionally, a first implementation for rewriting simple chains (as in
?s <p1>/<p2> ?o) is included.Depends on #2639 and #2653
Example:
Write and load the view for
geo;hasGeometry/geo:asWKT:Then use it implicitly in queries: With variable subject:
or with fixed subject: