[
https://issues.apache.org/jira/browse/JENA-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-626:
---
Assignee: (was: Andy Seaborne)
> SPARQL Query Caching
>
>
>
[
https://issues.apache.org/jira/browse/JENA-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-626:
---
Assignee: Saikat Maitra
> SPARQL Query Caching
>
>
> Key: JENA-626
On 17/10/15 11:29, Saikat Maitra wrote:
Hi
As we discussed I have implemented the first version of the SPARQL Query
Caching and raised my first PR. :)
:-)
It's good to see this.
https://github.com/apache/jena/pull/95
Please review and share feedback
We are commenting using github -
Hi
As we discussed I have implemented the first version of the SPARQL Query
Caching and raised my first PR. :)
https://github.com/apache/jena/pull/95
Please review and share feedback
Regards
Saikat
On Fri, Mar 13, 2015 at 10:30 PM, Saikat Maitra
wrote:
> Hello Andy,
On 06/03/15 02:21, Saikat Maitra wrote:
Hello,
I wanted to clarify few points related to separate service end point for
the SPARQL Query Caching feature. I was considering to take up either of
the below approach to implement the cache service end point. I am open for
both the approach and
On 13/03/15 12:37, Andy Seaborne wrote:
To check my understanding, let me put that in my own words: This is
essentially fronting the Fuseki server with another webapp that
intercepts all requests to the Fuseki server. (All requests because
it has to see update to manage the cache).
[...]
Hello Andy, Osma,
Thank you for your feedback.
I am also more inclined towards option 2 to implement the SPARQL_Cache
servlet as part of Fuseki. The fact that it will have access to Fuseki
internal and admin console makes a lot of sense.
I really like the idea of selective CacheEntry
Hello,
I wanted to clarify few points related to separate service end point for
the SPARQL Query Caching feature. I was considering to take up either of
the below approach to implement the cache service end point. I am open for
both the approach and wanted to discuss further.
Option 1 : create
[
https://issues.apache.org/jira/browse/JENA-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Vesse updated JENA-626:
---
Labels: java linked_data rdf sparql (was: gsoc java linked_data rdf sparql)
SPARQL Query Caching
[
https://issues.apache.org/jira/browse/JENA-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-626:
---
Labels: gsoc java linked_data rdf sparql (was: gsoc gsoc2014 java
linked_data rdf sparql)
SPARQL
[
https://issues.apache.org/jira/browse/JENA-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-626:
---
Labels: gsoc gsoc2014 java linked_data rdf sparql (was: gsoc gsoc2014)
SPARQL Query Caching
11 matches
Mail list logo