[
https://issues.apache.org/jira/browse/JENA-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15022591#comment-15022591
]
ASF GitHub Bot commented on JENA-626:
-------------------------------------
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/95#issuecomment-159011031
@afs Yes, I work on other projects where that is the case. My feeling is
that (irrespective of policy) it's good form to squash down, not all the way to
one commit, but down to a reasonable number that properly package the
substantive changes at play. But as I said, I didn't mean to imply that Jena
has some particular policy and I'm sorry if I caused any confusion. On a
semi-related note, there are a lot of merge commits in this PR. @samaitra, it's
of course your choice as to how to work, but if you are not familiar with `git
rebase`, it can be really helpful when trying to stay up to date with an
upstream master as you work.
> 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)
