afs commented on issue #1581: URL: https://github.com/apache/jena/issues/1581#issuecomment-1279993073
Thanks for the investigation. Upgrading Lucene is always a slight roadbump because of file format changes. All these issues will need to be in the release announcement. This would be good to pre-announce on users@jena and dev@jena and ask for feedback. Versions: IIRC (and it's been a while so caution!) `lucene-backwards-codecs` avoids the need to reload data on a major version change. Is this still true this time? JUL: Weird choice at this stage in the lifetime of Lucene. Use `jul-so-slf4j` - it's used elsewhere in Jena. We don't assume Log4j2 is the providing logging system - could be logback. There is no way round the potentially cyclic setup if the app wants JUL as the providing logging system - it'll have to exclude `jul-so-slf4j` itself. (This is includes one of my own projects! JUL is nice and light when you just want logging messages out.) StandardAnalyzer: Not sure whether we should set `EnglishAnalyzer.ENGLISH_STOP_WORDS_SET` in java (compatibility) or use this point in time to make the jump. `StandardAnalyzerAssembler` is impacted. Another "ask" on users@ thing. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
