Github user afs commented on the issue:
https://github.com/apache/jena/pull/95
Another use case:
In my day-job, we have a local (same JVM) database because calling to a
remote database (even same datacenter) is too expensive. RDF is used to drive
the UI for HTTP/HTML requests. This means we get a lot of small calls into the
database for every single HTTP request. Going off machine for each call does
not work. Getting larger parts of the RDF (i.e. a few large remote calls) only
gets us into having a local graph and many calls to that.
We can of course add our own caching because we control the whole stack but
it suggests a design whereby caching is done by the `QueryExecution` and not as
part of Fuseki HTTP request handling, either specific to Fuseki or as a general
feature in ARQ.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
