Aklakan commented on PR #3511:
URL: https://github.com/apache/jena/pull/3511#issuecomment-3951257429
My feeling is, that ideally on the ARQ level there should be just one
delegate which goes to the jena-rdflink module and then any actual
implementation happens via `{Query|Update}ExecDatasetBuilderOverRDFLink`.
However, I can think of e.g. the virtuoso jena adapter going through the arq
layer:
https://vos.openlinksw.com/owiki/wiki/VOS/VirtJenaProvider
> Bypass Jena/ARQ parser
> To use Virtuoso-specific SPARQL extensions (such as bif:contains), queries
must bypass the Jena/ARQ parser and go straight to the Virtuoso server. This is
done by using the VirtuosoQueryExecutionFactory.create() method, instead of and
without the Jena-specific QueryFactory.create() method, which always invokes
the Jena/ARQ parser, which in turn rejects any Virtuoso-specific extensions.
Thus one would execute a query as follows to bypass the Jena parser --
```
VirtuosoQueryExecution vqe = VirtuosoQueryExecutionFactory.create (query,
set);
vqe.execSelect();
-- rather than --
Query sparql = QueryFactory.create(query);
VirtuosoQueryExecution vqe = VirtuosoQueryExecutionFactory.create (sparql,
set);
vqe.execSelect();
```
With the SparqlAdapterRegistry indirection, this could become a conventional
`QueryFactory.create(query);`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
