The users@ message said "a few weeks" and I was all set to do the release ...

Then the JENA-450 report came in. JENA-450 is the problem that code can't create OntModels inside read transactions when the model is new -- it tries to set prefixes and read-only really is read-only.

The OntModelImpl constructor copies in prefixes from the profile. If the model is new, the prefixes aren't defined in the model, and the code sets them. But it can't.

A couple of possible fixes:

1/ Put try{} around the setNsPrefix loop and skip if an exception occurs.

2/ Always have an updatable in-memory prefix mapping for read-only model.

(2) seems better but I'm not absolutely sure how to achieve it yet within the current mechanism.

Long term, beyond 2.10.1, changing the design of TDB graphs to have graphs work across transaction boundaries looks like the right thing to do. The graph also carries around internal details used by the query execution engine. Then model.begin/model.commit can work as a write transaction. Not the sort of thing to do just before a release after people have tested for us.

For this release, I suggest a short amount of time to see if there is some temporary fix for JENA-450 (e.g. 1), then do the release regardless. This isn't a regression; it does need fixing; there are many other things in 2.10.1 that are better than 2.10.0.

        Andy

On 08/05/13 03:14, Stephen Owens wrote:
+1, love to have this version.


On Tue, May 7, 2013 at 8:09 PM, Rob Vesse <[email protected]> wrote:

Yes things look good, I don't think I have anything else that I need/want
to get into the release

Rob



On 5/7/13 6:45 AM, "Andy Seaborne" <[email protected]> wrote:

So far, so good.

There have been some useful reports, including SDB, and some
fixes/additions:

+ Added improved Fuseki start script

+ OpAsQuery fix rewriting nested selects

+ Optimizer improvement for DISTINCT and ORDER BY

+ Serializing queries for SERVICE: property paths could break the syntax.

+ One significant fix to RIOT in the handling file: URIs mostly
affecting Windows

+ Query timeouts now work as advertised


JENA-447 is SDB related but it's not a regression as far as I can see.
(Seems to be something with concurrent, transactions and the bulk loader.)

       Andy






Reply via email to