[
https://issues.apache.org/jira/browse/MARMOTTA-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13701937#comment-13701937
]
Sebastian Schaffert commented on MARMOTTA-255:
----------------------------------------------
Hi Peter, if you want to you might want to have a look at the
"kiwi-tripletable" module. I implemented efficient in-memory querying (with
SPOC and CSPO indexes) over statement Sets there. This code originates in the
old KiWi transaction model, where transactions could be 100k triples in size,
and iterating them for listing triples with certain subject and predicate was a
serious performance issue. The new code anyways binds transactions to database
transactions and does not really need this data structure. But for a
ModelRepository it might be worthwhile.
> 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
