[
https://issues.apache.org/jira/browse/JENA-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15002210#comment-15002210
]
ASF GitHub Bot commented on JENA-624:
-------------------------------------
Github user afs commented on the pull request:
https://github.com/apache/jena/pull/94#issuecomment-156132377
Great.
You don't need `/testing`. The material under there is for testing query
execution, not the dataset storage.
For functional tests, `AbstractDatasetGraphTests` and others in that
package should be enough. It's all programmatic, not script driven.
There are other sets around that might be worth at least checking they
work, and if not, put more tests in the datasetgraph programmatic tests
("testing the tests"). e.g. We can try to feed it through the SPARQL test suite
as a one-off but they aren't parameterized to implementation. They test ARQ,
not the dataset storage and if theer are failures, they should be captured in
dataset tests.
I have some more tests (coverage of code paths in `DatasetGraphBaseFind`)
which I'll put in but after this is merged so we have a stable base to get the
merge done.
> 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: gsoc, gsoc2015, 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)
