[
https://issues.apache.org/jira/browse/MARMOTTA-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677942#comment-13677942
]
Peter Ansell commented on MARMOTTA-255:
---------------------------------------
So the idea is to efficiently implement the following SPARQL query in the Sail
API, and then also expose the functionality in the Repository API?
SELECT DISTINCT ?subject WHERE { ?subject ?predicate ?resource }
Feel free to open an issue on the sesame tracker once you have a proposal.
Some of these functions are available in the new Sesame-2.7 Model API if you
want to implement something that is similar to that for consistency. Ie,
Model.subjects(), Model.predicates(), Model.objects().
> Listing Resources needs to be more efficient
> --------------------------------------------
>
> Key: MARMOTTA-255
> URL: https://issues.apache.org/jira/browse/MARMOTTA-255
> Project: Marmotta
> Issue Type: Improvement
> Components: Sesame Tools, Triple Store
> Affects Versions: 3.0-incubating, 3.1-incubating
> Reporter: Sebastian Schaffert
> Assignee: Sebastian Schaffert
>
> Listing resources is currently based on listing triples and projecting the
> subject resource. The functionality to list all resources is often needed in
> a Linked Data server and could be supported directly be KiWi through a much
> more efficient SQL query.
> To support this functionality, it is however necessary to extend the Sesame
> API a bit, both at the level of the Repository API and at the level of the
> Sail API. This could probably be done by interfaces that add the additional
> methods and a subclassed SailRepository/SailRepositoryConnection.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
