[
https://issues.apache.org/jira/browse/MARMOTTA-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815091#comment-13815091
]
ASF subversion and git services commented on MARMOTTA-245:
----------------------------------------------------------
Commit e7692e68bdcae9e1d988cbd9cc108ab0631bb402 in branch refs/heads/develop
from [~wastl]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-marmotta.git;h=e7692e6 ]
improved KiWi bulk import (MARMOTTA-310, MARMOTTA-245)
> Possible solutions for improving triple store's storage and retrieve
> performance.
> ---------------------------------------------------------------------------------
>
> Key: MARMOTTA-245
> URL: https://issues.apache.org/jira/browse/MARMOTTA-245
> Project: Marmotta
> Issue Type: Improvement
> Components: Triple Store
> Affects Versions: 3.0-incubating
> Reporter: Sergio Fernández
> Assignee: Raffaele Palmieri
> Fix For: 3.2
>
>
> This issue was born by an initial idea about improvement for triples storage
> and collects all subsequent ideas about the same argument.
> In the order:
> 1)Use db native methods for bulk import
> 2)Jena storage
> 3)Triple store on top of a NoSQL database
> For the point 1, for retaining record transactionality and integrity, it
> would require a ploy(e.g. maintenaince mode), on the other hand a lot of
> improvements of codebase have been with introduction of JDBC Batch API and
> there are significant results.
> The point 2 depend on MARMOTTA-85, 88 and 89.
> The point 3 is an unexplored path , and could mean adopting an approach close
> to that described in "Rya: A Scalable RDF Triple Store for the Clouds";
> however, that could be the most difficult path to explore for the impacts on
> actual codebase.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
