[
https://issues.apache.org/jira/browse/MARMOTTA-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700370#comment-13700370
]
Peter Ansell commented on MARMOTTA-255:
---------------------------------------
There isn't a current implementation of a ModelRepository in the Sesame
codebase (or ModelSail with SailRepository wrapper). It shouldn't be too hard
to develop, as the TripleSource interface should map fairly easily onto a
Model. The Model API only moved from Alibaba to Sesame in 2.7 so there haven't
been many uses of it yet.
I have only really started using Model since implementing the new Rio.parse and
Rio.write methods that make it much easier than MemoryStore, but I have missed
the ability in some cases to perform SPARQL queries on the Model so I have had
the thought drifting around for a few months now. I have started programming a
little differently though, using loops over Model.subjects() or Model.objects()
or Model.filter(...).subjects() where I was previously using simple SPARQL
queries.
Efficiently implementing the Model API directly over a particular
Sail/Repository would also have benefits that you could use to speed up queries
in KiwiConnection, for example. The Model API would be tracked directly to the
source instead of having to go through the standard Sail methods. One issue
with that may be that Model doesn't have any checked exceptions on its methods,
as it was designed to be an in-memory API.
> 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
