[ https://issues.apache.org/jira/browse/LUCENE-9450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17383532#comment-17383532 ]
Gautam Worah commented on LUCENE-9450: -------------------------------------- That makes sense to me. Naive question: If the user has 4 old StoredFields based segments and 1 new BinaryDocValues based segment (like the way you just described), does force merging them to 1 produce a single BinaryDocValues based segment? Also, I think, most Lucene users would have a system for reindexing documents as compared to force merging segments to one, so I guess the recommended approach for them would be to just reindex. I see that in the older {{lucene-solr}} repo, we had a migrate.txt file with instructions to how to migrate to newer Lucene versions, do we plan to produce something similar for the transition to Lucene 9.0. If yes, we should definitely mention the change in field type for the taxonomy index and some migration instructions. I can add those instructions > Taxonomy index should use DocValues not StoredFields > ---------------------------------------------------- > > Key: LUCENE-9450 > URL: https://issues.apache.org/jira/browse/LUCENE-9450 > Project: Lucene - Core > Issue Type: Improvement > Components: modules/facet > Affects Versions: 8.5.2 > Reporter: Gautam Worah > Priority: Minor > Labels: performance > Fix For: main (9.0) > > Attachments: LUCENE-9450-localrun.py-v1, wip_taxonomy_patch > > Time Spent: 3h 50m > Remaining Estimate: 0h > > The taxonomy index that maps binning labels to ordinals was created before > Lucene added BinaryDocValues. > I've attached a WIP patch (does not pass tests currently) > Issue suggested by [~mikemccand] -- 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