Aklakan commented on issue #1314:
URL: https://github.com/apache/jena/issues/1314#issuecomment-1150148309
My limited understanding in of the LOOP variables is as follows:
```
?s ?p ?o .
LOOP (?s) {
?s ?p ?o # becomes ?s ?/p ?/o
LOOP (?p) {
?s ?p ?o # becomes ?/s ?/p ?//o
}
LOOP (?s ?p) {
?s ?p ?o # ?s becomes ?s ?/p ?///o
}
}
```
For my work on the plugin: With the current approach I am just reverting the
scope of all variables - it's as if all mentioned variables appeared as loop
variables. I'd think for a first version of a service executor plugin marked as
experimental its ok to have this behavior documented; the implication is that
one might have to be a bit careful of the variable naming in inner queries.
This way it's not a blocker for me.
I think I am now working on the last problem for finishing the functionality
of the PR: dealing with unknown result set limits in the cache:
A service clause with caching and/or bulk enabled should yield the exact
same result as if these modifiers are absent.
This means I need to fiddle in some logic tha considers the 'largest seen
result set size on a service so far' and which avoids serving data from cache
if it cannot be guaranteed that the invisible result set size limit will be
adhered to.
--
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]
