[
https://issues.apache.org/jira/browse/LUCENE-9248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17043766#comment-17043766
]
David Smiley commented on LUCENE-9248:
--------------------------------------
WDYT [~jpountz]? Are all users of {{Lucene84PostingsWriter}} / Reader affected,
thus nearly all formats?
If we do a 8.4.1 I think this should be released in such a bug-fix version.
In this issue I'd also like to update the Solr docs on the text tagger to
suggest the FST format as more of a tip with a caveat. And also add to the
upgrade notes on Lucene & Solr sides.
> Change internal code names of postingsFormats to use 84 suffix
> --------------------------------------------------------------
>
> Key: LUCENE-9248
> URL: https://issues.apache.org/jira/browse/LUCENE-9248
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/codecs
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Major
>
> Some postings formats write the postings differently as of Lucene 8.4 due to
> changes -- LUCENE-9027 and LUCENE-9116. Blocktree was transitioned in a
> backwards-compatible way but some (all?) others were not. Consequently an
> attempt of the new version to read an old index will fail due to some
> non-obvious error. I propose here using a simple version suffix on these
> postings formats like "84" (thus "FST84" as one example). I see some already
> use a suffix but were not bumped for 8.4. This is a really simple change and
> doesn't address the problem of us not noticing future needs to version bump.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
