Cool. The extension points are basically TripleTable and QuadTable, because of the constructor DatasetGraphInMemory(QuadTable, TripleTable). Someone could offer their own impls and use that (public) constructor.
--- A. Soroka The University of Virginia Library > On Dec 9, 2015, at 3:38 PM, Andy Seaborne <[email protected]> wrote: > > On 09/12/15 15:19, A. Soroka wrote: >> Here: >> >> https://gist.github.com/ajs6f/463117f0d0e094ffefc5 >> >> are some suggested edits for that doc, mostly just typo-fixes and >> suggestions for clarification. > > Done, thanks. > >> Other questions from me: >> >> 1) Is it worth creating a component in Jira to track tickets for this stuff? > > I think incoming JIRAs won't be simple to associate with this one component. > We can see how it goes but the various differences in the datasets are more > likely the issues. Just a guess. > >> >> 2) Shall I write up a simple page describing the impl and more importantly, >> extension points? > > Always useful, not urgent. > > (What are the extension points?) > > Andy > >> >> --- >> A. Soroka >> The University of Virginia Library >> >>> On Dec 9, 2015, at 5:20 AM, Andy Seaborne <[email protected]> wrote: >>> >>> I put some documentation in at >>> >>> http://jena.staging.apache.org/documentation/rdf/datasets.html >>> >>> because the announcement needs to link to something. I hope I got it >>> right. This can be changed between releases -- the bytes aren't in the >>> release itself. >>> >>> (The file name was chosen so that more general text could go there and this >>> becomes a section of documentation about dataset usage in Jena) >>> >>> Andy >>> >>> On 08/12/15 14:53, A. Soroka wrote: >>>> That should certainly “enlist” a number of RC testers. {grin} >>>> >>>> I will stand by for bug fixes. >>>> >>>> --- >>>> A. Soroka >>>> The University of Virginia Library >>>> >>>>> On Dec 8, 2015, at 3:38 AM, Andy Seaborne <[email protected]> wrote: >>>>> >>>>> On 23/11/15 15:31, A. Soroka wrote: >>>>>> A weightless +1 from me, of course! {grin} I’m excited to see this stuff >>>>>> get in front of people. >>>>>> >>>>>> I’m not sure what you mean by “Fuseki integration”, Andy. Do you mean to >>>>>> make the new dataset impl available as an option in Fuseki (presumably >>>>>> in both the web admin UI and the CLI for the standalone server)? >>>>> >>>>> Fuseki should chnage to using the new in-memory txn dataset when creating >>>>> new in-memory setups. So the template-driven assemblers (UI) and from >>>>> the command line (--mem) will change. Existing setups are preserved >>>>> because the template is used to create an assembler when first used, not >>>>> each start-up. >>>>> >>>>> Andy >>>>> >>>>>> >>>>>> --- >>>>>> A. Soroka >>>>>> The University of Virginia Library >>>>>> >>>>>>> On Nov 23, 2015, at 10:24 AM, Andy Seaborne <[email protected]> wrote: >>>>>>> >>>>>>> We have: >>>>>>> >>>>>>> * in-memory transactional dataset from Adam is in the codebase >>>>>>> (details on progress below) >>>>>>> * configurable lucene analyzers >>>>>>> * general maintenance. >>>>>>> * Improved start-up and configuration to wire the jars together. >>>>>>> >>>>>>> Shall we do a release? This fits our 3-6 months cycle. >>>>>>> >>>>>>> As we know, getting people to try unreleased builds has limited effect >>>>>>> (generally for point-bug fixes, less so for new features) so my >>>>>>> suggestion is to release soon as v3.0.1 and describe the in-memory >>>>>>> transactional dataset as "RC". It's not fully integrated (test: Fuseki >>>>>>> is not using it yet) and getting that done and stable isn't an instant >>>>>>> task to do. At the same time, a release will let people try it. >>>>>>> >>>>>>> So we expose the in-memory transactional dataset at the API level now, >>>>>>> introduce the deprecations so people can see what's coming, and >>>>>>> complete/stabilize the integration to make a v3.1.0 in a few months >>>>>>> time. >>>>>>> >>>>>>> Andy >>>>>>> >>>>>>> >>>>>>> Progress on the in-memory transactional dataset >>>>>>> https://pony-poc.apache.org/thread.html/Zj36f2pbaszgdnj >>>>>>> >>>>>>> If you want to try it, then DatasetFactory.createTxnMem() is the entry >>>>>>> point. >>>>>>> >>>>>>> -------------------------------------------------------- >>>>>>> >>>>>>> Outstanding tasks: >>>>>>> * Dependency version management in jena-parent. >>>>>>> >>>>>>> Done >>>>>>> >>>>>>> * more testing [done], and the organisation of the tests >>>>>>> >>>>>>> Test done, organisation of tests is partially done. There is a wider >>>>>>> tasks to organise the dataset tests we have into some sort of order but >>>>>>> that's non-blocking. >>>>>>> >>>>>>> * documentation >>>>>>> * code cleaning for deprecation of DatasetFactory.createMem >>>>>>> * Same migration for DatasetGraphFactory.createMem >>>>>>> * Fuseki integration >>>>>>> >>>>>>> -------------------------------------------------------- >>>>>>> >>>>>> >>>>> >>>> >>> >> >
