You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2015/11/14 15:55:11 UTC

[jira] [Updated] (JENA-624) Develop a new in-memory RDF Dataset implementation

     [ https://issues.apache.org/jira/browse/JENA-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Seaborne updated JENA-624:
-------------------------------
    Labels: java linked_data rdf  (was: gsoc gsoc2015 java linked_data rdf)

> Develop a new in-memory RDF Dataset implementation
> --------------------------------------------------
>
>                 Key: JENA-624
>                 URL: https://issues.apache.org/jira/browse/JENA-624
>             Project: Apache Jena
>          Issue Type: Improvement
>            Reporter: Andy Seaborne
>            Assignee: A. Soroka
>              Labels: java, linked_data, rdf
>
> The current (Jan 2014) Jena in-memory dataset uses a general purpose container that works for any storage technology for graphs together with in-memory graphs.  
> This project would develop a new implementation design specifically for RDF datasets (triples and quads) and efficient SPARQL execution, for example, using multi-core parallel operations and/or multi-version concurrent datastructures to maximise true parallel operation.
> This is a system project suitable for someone interested in datatbase implementation, datastructure design and implementation, operating systems or distributed systems.
> Note that TDB can operate in-memory using a simulated disk with copy-in/copy-out semantics for disk-level operations.  It is for faithful testing TDB infrastructure and is not designed performance, general in-memory use or use at scale.  While lesson may be learnt from that system, TDB in-memory is not the answer here.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)