Not sure what you mean by status, but I’m happy to look at any particular problems you’re seeing. I had no intentions of taking it any further on its own, for now. The persistent datastructure direction seems more interesting and profitable. I would be happy to straighten out any mistaken overruns over DSGWithLock’s semantics. Where are those documented? (For those who missed it, the journaling dataset came in as an early attempt to move forward with transactional in-mem storage, and seemed to work fine when the bulk of the work for JENA-624 that I did got merged.)
To be sure, the package is not in use in oaj.s.c.mem, which is where the more interesting work ended up, and I cannot imagine that it is in use by any great crowd since 3.0.1, so if you want to quash it, I’m not going to cavil. We’ll always have the version history… --- A. Soroka The University of Virginia Library > On Feb 2, 2016, at 4:29 PM, Andy Seaborne <[email protected]> wrote: > > Adam - what's the status of this package? > > While working on JENA-1089, I found that DatasetGraphWithRecord isn't calling > up into the inherited abort(). In refactoring and tightening up around > DatasetGraphWithLock, tests detect an error. It also means changes > monitoring wasn't working. > > While fixing some other timing/concurrency tests, mysterious things are > breaking in DatasetGraphWithLock, which it uses. DatasetGraphWithRecord seems > to pin down the semantics of DatasetGraphWithLock beyond the contract. > > If this package isn't in use, I'd rather not spend time puzzling it all out. > > Andy
