Skip to content

Feature/473 autonomous next query pipeline#484

Draft
remiceres wants to merge 3 commits into
feature/472-bridge-storage-manager-producerfrom
feature/473-autonomous-next-query-pipeline
Draft

Feature/473 autonomous next query pipeline#484
remiceres wants to merge 3 commits into
feature/472-bridge-storage-manager-producerfrom
feature/473-autonomous-next-query-pipeline

Conversation

@remiceres

Copy link
Copy Markdown
Contributor

Summary

This PR adds the first autonomous end-to-end SPARQL execution path for the next query pipeline.

It proves that simple queries can now run through:

SPARQL string -> next parser -> next AST -> next KGRAM -> StorageManagerProducer -> StorageManager

without using the legacy QueryProcess.

This PR is stacked on top of #472.

Changes

  • Configure ANTLR generated sources correctly for Gradle and IDEs.
  • Add UnsupportedQueryFeatureException for clear unsupported-feature errors.
  • Add next AST support for simple INSERT DATA and DELETE DATA.
  • Add CONSTRUCT support in CoreseAstQueryBuilder.
  • Add NextSparqlPipelineExecutor as an internal integration executor.
  • Add end-to-end tests for SELECT, ASK, CONSTRUCT, DESCRIBE, INSERT DATA, and DELETE DATA.

Scope

This is not the final public SPARQL API.

Unsupported SPARQL features fail explicitly.

@remiceres remiceres self-assigned this Jul 8, 2026
@remiceres remiceres added the Refactoring Issue created during the 2025 refactoring effort label Jul 8, 2026
@remiceres remiceres marked this pull request as draft July 9, 2026 08:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Refactoring Issue created during the 2025 refactoring effort

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BRIDGE] Execute all query types on the KGRAM egine using the new parser and a new producer, without using any of the legacy classes outside of KGRAM

1 participant