|Re: [rdf4j-dev] Newer Lucene Version|
> Good stuff, thanks Andreas. I'm not really familiar with the various lucene and solr versions, will this have any influence on existing > users with existing indexes? Or will it seamlessly upgrade?
it is my understanding that users are encouraged to reindex whenever there's a major (N+1) Lucene/Elasticsearch update...
And reindexing is probably required for upgrading to major version N+2 afterwards, because Lucene (or ES) is not guaranteed to be able read index from version N-2...
(I forgot which one, or maybe both, I have to re-read my own mails :-)
So it would be a good thing to mention reindexing in the release notes
From: rdf4j-dev-bounces@xxxxxxxxxxx <rdf4j-dev-bounces@xxxxxxxxxxx> on behalf of Jeen Broekstra <jeen.broekstra@xxxxxxxxx>
Sent: Thursday, May 24, 2018 1:11:09 AM
Subject: Re: [rdf4j-dev] Newer Lucene Version
On 23/5/18 18:42, Andreas Schwarte wrote:
> Hi Bart, all, > > the issue is now tracked in > https://github.com/eclipse/rdf4j-storage/issues/71 > > Also I provided an initial pull request with the current status to > https://github.com/eclipse/rdf4j-storage/pull/72 > > The updates of the Lucene Sail and Solr (Lucene 6.6.4 and Solr 6.6.4) > look solid already and tests are passing.
Good stuff, thanks Andreas. I'm not really familiar with the various lucene and solr versions, will this have any influence on existing users with existing indexes? Or will it seamlessly upgrade?
> Updating elasticsearch seems a bit more difficult. The code change > should be roughly fine (though I still left some preliminary comments > and TODO markers), however, I am still facing issues with the > integration test. It fails with errors complaining about a "JarHell", > i.e. different versions of transitive dependencies being loaded. I am > currently looking into the maven descriptors to see if I can resolve > this. > > Could someone of you already check the current PR and give feedback? > Especially the elasticsearch part, as I have never worked with it > before and do not have a testing environment. Lucen Sail I will test > in our test installation, so that I can definitely cover.
I'll have a closer look this weekend.
> Also one more question: the lucene based modules still use "URI" > instead of "IRI", should I also do the refactoring here? If you're up for it, by all means do.