[
https://issues.apache.org/jira/browse/JENA-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15002299#comment-15002299
]
ASF GitHub Bot commented on JENA-624:
-------------------------------------
Github user afs commented on the pull request:
https://github.com/apache/jena/pull/94#issuecomment-156148758
It is not the code - it's the way tests are found.
This is what seems to be happening - when running the JUnit tests on the
package (at least in Eclipse and I believe in surefire if we didn't use "TS_"),
`TestDatasetGraphInMemory`, `TestInMemory` and the inner class of
`TestDatasetGraphInMemory` all get found and run. But `TestInMemory` runs
`TestDatasetGraphInMemory`, and` TestDatasetGraphInMemory` runs it's inner
classes. So the tests run x3, one for each level. To check, I put a break
point on and it got hit three times.
(Also - running the same test more than on confuses Eclipse in minor ways -
some don't get marked as "run".)
No need to do anything now - lets get the code in.
> 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)
