[ https://issues.apache.org/jira/browse/JENA-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14965954#comment-14965954 ]
ASF GitHub Bot commented on JENA-626: ------------------------------------- Github user afs commented on the pull request: https://github.com/apache/jena/pull/95#issuecomment-149728229 cache Invalidation: it is very hard to know what an update (adds and deletes) will change. This includes hard cases like an aggregation count, or a SPARQL "NOT EXISTS". Dropping everything for one dataset is reliable and has no corner cases. The cache code is still useful - a lot of uses are for publishing where updates are rare and queries are frequent. > SPARQL Query Caching > -------------------- > > Key: JENA-626 > URL: https://issues.apache.org/jira/browse/JENA-626 > Project: Apache Jena > Issue Type: Improvement > Reporter: Andy Seaborne > Assignee: Saikat Maitra > Labels: java, linked_data, rdf, sparql > > Add a caching layer to Fuseki to cache the results of SPARQL Query requests. > This cache should allow for in-memory and disk-based caching, configuration > and cache management, and coordination with data modification. -- This message was sent by Atlassian JIRA (v6.3.4#6332)