Recorded as JENA-1621

Chris - thanks for tracking down the versions.

> It seems like a good idea to try and migrate rather than getting stuck > in a situation where there’s a larger mountain to climb and the index > updater for Lucene 8.x won’t work with Jena versions using Lucene
> 6.4.1.

+1
Better to have the option to run the in--place upgrade tool
though some people will need to reindex.

    Andy

On 27/10/2018 18:18, Chris Tomlinson wrote:
The indexes have to be upgraded following the directions at 
https://lucene.apache.org/solr/guide/7_5/indexupgrader-tool.html 
<https://lucene.apache.org/solr/guide/7_5/indexupgrader-tool.html>, as you’ve 
noted.

The indexes for Lucene versions earlier than 6.x can not be converted directly 
to 7.x, thus users running on Jena prior to 3.3.0 (released 21 May 2017) will 
have to reload their data when moving to a Jena with Lucene 7.x.

There are quite a few changes noted at 
https://lucene.apache.org/core/7_5_0/MIGRATE.html 
<https://lucene.apache.org/core/7_5_0/MIGRATE.html> that could impact Jena 
users. In particular:

Changed SPI lookups for codecs and analysis changed (LUCENE-7873 
<https://issues.apache.org/jira/browse/LUCENE-7873>)

Due to serious problems with context class loaders in several frameworks (OSGI, 
Java 9 Jigsaw), the lookup of Codecs, PostingsFormats, DocValuesFormats and all 
analysis factories was changed to only inspect the current classloader that 
defined the interface class (lucene-core.jar). Normal applications should not 
encounter any issues with that change, because the application classloader 
(unnamed module in Java 9) can load all SPIs from all JARs from classpath.

. . .

and

CustomAnalyzer resources (LUCENE-7883 
<https://issues.apache.org/jira/browse/LUCENE-7883>)##

Lucene no longer uses the context class loader when resolving resources in 
CustomAnalyzer or ClassPathResourceLoader. Resources are only resolved against 
Lucene's class loader by default. Please use another builder method to change 
to a custom classloader.

and

AnalyzingQueryParser removed (LUCENE-7355 
<https://issues.apache.org/jira/browse/LUCENE-7355>)

The functionality of AnalyzingQueryParser has been folded into the classic 
QueryParser, which now passes terms through Analyzer#normalize when generating 
queries.

This last one is already noted implicitly in Jean-Marc Vanel’s note 
<http://mail-archives.us.apache.org/mod_mbox/jena-users/201810.mbox/%3ccanwvfkbhygwgchb1mzwxn1rnw-n6qb9zyqamkmh-vozgpoa...@mail.gmail.com%3E>.

I’m not sure what all needs to be checked to determine how the class loader 
changes may impact Fuseki and other Jena deployments.

There have been quite a few improvements and fixes in the geo-spatial 
functionality.

It seems like a good idea to try and migrate rather than getting stuck in a 
situation where there’s a larger mountain to climb and the index updater for 
Lucene 8.x won’t work with Jena versions using Lucene 6.4.1.

I’m willing to look more deeply at this. I have a bug fix for jena-text 
highlighting that I’ll raise an issue and a PR for next week.

Regards,
Chris


On Oct 27, 2018, at 5:53 AM, Andy Seaborne <a...@apache.org> wrote:

Comments?

Do Lucene 6 indexes work with Lucene 7 code or do they require explicit 
upgrading?

https://lucene.apache.org/solr/guide/7_5/indexupgrader-tool.html

    Andy

-------- Forwarded Message --------
Subject: Lucene dependency could be upgraded
Date: Wed, 24 Oct 2018 13:31:46 +0200
From: Jean-Marc Vanel <jeanmarc.va...@gmail.com>
Reply-To: us...@jena.apache.org
To: Jena users <us...@jena.apache.org>

Jena text 3.9.0 is at Lucene 6.4.1 , while the last Lucene is 7.5.0 :
https://mvnrepository.com/artifact/org.apache.jena/jena-text/3.9.0

Trying to upgrade brings
ClassNotFoundException:
org.apache.lucene.queryparser.analyzing.AnalyzingQueryParser

This happens in class TextIndexLucene.

--
Jean-Marc Vanel
http://www.semantic-forms.cc:9111/display?displayuri=http://jmvanel.free.fr/jmv.rdf%23me#subject
<http://www.semantic-forms.cc:9111/display?displayuri=http://jmvanel.free.fr/jmv.rdf%23me>
Rule-based programming, Semantic Web
+33 (0)6 89 16 29 52
Twitter: @jmvanel , @jmvanel_fr ; chat: irc://irc.freenode.net#eulergui
Chroniques jardin
<http://semantic-forms.cc:1952/backlinks?q=http%3A%2F%2Fdbpedia.org%2Fresource%2FChronicle>



Reply via email to