Feature/471 next query legacy execution#480
Merged
remiceres merged 2 commits intoJul 3, 2026
Merged
Conversation
|
Test Results 428 files 428 suites 21s ⏱️ Results for commit d1425ec. |
abdessamad-abdoun
approved these changes
Jul 3, 2026
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
2 participants
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 adds coverage for #471.
It verifies that SELECT queries parsed by the Corese-next parser and compiled into a next KGRAM Query can be executed by the legacy QueryProcess over a legacy Graph.
It also fixes the KGRAM representation of variable predicates: a pattern like
?s ?p ?onow exposes the KGRAM root property as the edge node and?pas the edge variable.