Osma - no rush, when you have time.
If it works better for you, I can do these before and get them into
snapshots to confirm everything.
Andy
On 09/03/17 13:34, Osma Suominen wrote:
Hi Andy!
I will try to get the Lucene upgrade in soon. I just want to catch the
exceptions caused by trying to use an old index and inform the user
about the need to recreate the index, as Rob suggested.
-Osma
09.03.2017, 15:03, Andy Seaborne kirjoitti:
Thee are some JIRA outstanding I have in progress. With the update of
Lucene coming up, I wanted to report where I was.
I'll hold back on all changes so as not to make it more fiddly for the
Lucene switch. I don't think any affect Lucene at all.
JENA-1302 : Lucene commit error
I think I have found the problem in DatasetGraphText. A change of
Lucene version will not help - it's a Jena bug of failing to lock
briefly during the commit to both Lucene and TDB. A first pass fix
worked for me - I want to do a deeper analysis and checking before
applying a fix to the codebase.
(TDB2's general transaction system can handle this better.)
JENA-1306: RDFParser
PR#222
This is ready to go in. This is not a bug fix so waiting for a bit is
fine.
It'll help PR#211 (JSON-LD and preserving bnode labels)
JENA-1300 "Using alternative path in Fuseki runs forever"
To do anything about this report, it needs an executable test case. If
that is not forth coming, I intend to close this; it seems to relate to
the shape of the data. I'm not going to guess at possibilities in the
hope I stumble across something. I have not a response to a change to
the query to see what happens.
Andy
