You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "Olivier Grisel (JIRA)" <ji...@apache.org> on 2011/03/18 11:47:34 UTC
[jira] Created: (CLEREZZA-466) Make Jena TDB storage able to
perform native SPARQL queries
Make Jena TDB storage able to perform native SPARQL queries
-----------------------------------------------------------
Key: CLEREZZA-466
URL: https://issues.apache.org/jira/browse/CLEREZZA-466
Project: Clerezza
Issue Type: Improvement
Reporter: Olivier Grisel
Currently sparql engines and triple store implementations are fully isolated by a generic wrapper that prevent TDB backed store to perform sparql queries as efficiently as possible.
Proposed solution by Reto on the developers mailing list:
TcProvider can Implement an additional Subinterface (say SparqlTcProvider) allowing to pass Sparql-queries to them. If a sparql query affects only graphs provided by the same SparqTcProvider the the query is forwarded to that provider, otherwise the current process applies.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CLEREZZA-466) Make Jena TDB storage able to
perform native SPARQL queries
Posted by "Olivier Grisel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLEREZZA-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Grisel updated CLEREZZA-466:
------------------------------------
Description:
Currently sparql engines and triple store implementations are fully isolated by a generic wrapper that prevents TDB-backed stores to perform sparql queries as efficiently as possible.
Proposed solution by Reto on the developers mailing list:
TcProvider can Implement an additional Subinterface (say SparqlTcProvider) allowing to pass Sparql-queries to them. If a sparql query affects only graphs provided by the same SparqTcProvider the the query is forwarded to that provider, otherwise the current process applies.
was:
Currently sparql engines and triple store implementations are fully isolated by a generic wrapper that prevent TDB backed store to perform sparql queries as efficiently as possible.
Proposed solution by Reto on the developers mailing list:
TcProvider can Implement an additional Subinterface (say SparqlTcProvider) allowing to pass Sparql-queries to them. If a sparql query affects only graphs provided by the same SparqTcProvider the the query is forwarded to that provider, otherwise the current process applies.
> Make Jena TDB storage able to perform native SPARQL queries
> -----------------------------------------------------------
>
> Key: CLEREZZA-466
> URL: https://issues.apache.org/jira/browse/CLEREZZA-466
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Olivier Grisel
>
> Currently sparql engines and triple store implementations are fully isolated by a generic wrapper that prevents TDB-backed stores to perform sparql queries as efficiently as possible.
> Proposed solution by Reto on the developers mailing list:
> TcProvider can Implement an additional Subinterface (say SparqlTcProvider) allowing to pass Sparql-queries to them. If a sparql query affects only graphs provided by the same SparqTcProvider the the query is forwarded to that provider, otherwise the current process applies.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira