[ https://issues.apache.org/jira/browse/JENA-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15002246#comment-15002246 ]
ASF GitHub Bot commented on JENA-624: ------------------------------------- Github user afs commented on the pull request: https://github.com/apache/jena/pull/94#issuecomment-156140079 All this can be refined post merge. I've been checking that the existing test hierarchies run as well. `TestDatasetGraphInMemory` and `TestInMemory` seem to both call `TestDatasetGraphInMemory`. To make it clear what's a suite and what are the tests, ARQ uses a convention that "TS_" are suites and `Test*` are the `@Test`s themselves (and occasionally `TC_` are collections of suites, e.g. RIOT vs ARQ). It's just a style thing and in a large set of tests, a bit of control over order (building blocks before combinations helps in navigating failures. Putting each nested class in `TestDatasetGraphInMemory` in a separate files and having TS_ makes navigation a bit easier in an IDE. [All "IMO".] > 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)