-
Notifications
You must be signed in to change notification settings - Fork 652
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
Interaction of GRAPH graph patterns and subqueries #2793
Comments
Can you provide details of what your storage setup is e.g.
In algebra terms these end up being different algebra's which likely explains the difference in results. Your first query yields the following algebra:
While your second yields the following algebra:
Notice that with the
That shouldn't ever be the case, the way a |
I am using fuseki with TDB2 # for starting the server
java -jar fuseki-server.jar --update --tdb2 --loc=databases/testing /endpoint I am using the default config file found in
I see. It makes sense, thank you |
@nkaralis -- thank for the report. The unbound @rvesse's analysis is correct (a simpler reproduction below). TDB is the main user of quad-based execution but its available for in-memory as well:
and
giving
|
Version
5.2.0
Question
Hello,
I have some questions about the interaction of GRAPH graph patterns and subquries.
I am using version 5.2.0.
Assume the scenario described below.
First, I load a graph into two separate named graphs.
Both graphs contain 16 triples.
The query provided below, returns the triples found in both graphs, which results in 32 solutions. Here,
?g
is always unbound.The query provided below also returns 32 results. In this case,
?g
is always assigned a value (i.e.,<http://www.example.org/graph1>
or<http://www.example.org/graph2>
)I have the following questions:
For both queries, I was expecting 64 results: Cartesian product between the results of the subqueries (32 results) and the possbible values for
?g
(2 named graphs).Thank you in advance.
The text was updated successfully, but these errors were encountered: