Skip to content
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

COMUNICA: support custom comunica configurations #122

Closed
jacoscaz opened this issue Nov 28, 2020 · 2 comments
Closed

COMUNICA: support custom comunica configurations #122

jacoscaz opened this issue Nov 28, 2020 · 2 comments

Comments

@jacoscaz
Copy link
Owner

As of v7.1.0, quadstore does not support any Comunica configuration other than quadstore-comunica, which optimizes for bundle size and dependency count to deliver the smallest possible Comunica configuration that still manages to evaluate queries.

comunica-quadstore does not include anything else but the subset of actors that are required to get from a SPARQL non-federated query to its RDF/JS results, leaving out parsers, serializers, federation, GraphQL and a bunch of other features supported by Comunica.

We should probably allow developers to pass custom engine factory functions to quadstore's constructor.

@jacoscaz jacoscaz modified the milestones: v7.1.0, v7.2.0 Nov 28, 2020
@jacoscaz
Copy link
Owner Author

Released with quadstore@8.0.0-alpha.3 (watch out for the new required constructor option!).

@markmelville
Copy link

I'm experimenting with quadstore as a server that fronts a small amount of data, in a distributed linked data network. As such, I'd like to be able to execute federated queries.

This issue and its resolution seem to indicate that, although quadstore-comunica has chosen not to implement it, I should be able to provide a custom function. I can't find any examples, docs, or code that is helping me to see how to do this. Can anyone provide some pointers? Thanks in advance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants