-
Notifications
You must be signed in to change notification settings - Fork 11
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
No results on re-execution of a TREE query using the same blank node has a object and a subject #102
Comments
Query re-execution seems to work fine with regular link traversal AFAIK. |
At least on my end it does not. I has to be noted that the execution must have ended, for the bug to manifest. |
I see, so it's a higher-level problem indeed. |
I just realized that this may be the same problem as discovered in comunica/comunica#1180 (comment). |
This caused problems related to dataset-level cardinalities that were found in the initial source being overridden without proper accumulation with exact cardinalities from later sources Closes #1156 Closes #1180 May be related to comunica/comunica-feature-link-traversal#102
This caused problems related to dataset-level cardinalities that were found in the initial source being overridden without proper accumulation with exact cardinalities from later sources Closes #1156 Closes #1180 May be related to comunica/comunica-feature-link-traversal#102
This refactors internal metadata handling so that it can be incrementally updated. Metadata objects now have a `state` field, which represents their validation state, which can be invalidated, and be listened to. This allows actors to listen to metadata invalidations and act upon changes. This commit also adds a metadata accumulation bus that abstracts the logic for merging metadata from multiple sources that existed before in the federated actor. This will enable this logic to be used in other places, and for other actors to manage how metadata is merged. Closes #1156 Closes #1180 May be related to comunica/comunica-feature-link-traversal#102
Ok, the changes in Comunica indeed seem to have solved this problem as well 🎉 |
Sadly, the problem still manifests itself when we rerun the query on the demo engine. |
@constraintAutomaton Could you check again with the new code in comunica v3? |
Yes it seems to be working now! |
I realize that when I'm running a query that has a variable that will be a blank node and that variable is reused as a subject than when I rerun the query the engine will produce no result. For illustration let's consider this query
where
?relation
will be a blank node.if instead I'm running this query
or that query
I'm not having this problem. Which make me think that the reused of the blank node might be the problem.
Here a link of an example using the engine
The text was updated successfully, but these errors were encountered: