[
https://issues.apache.org/jira/browse/LUCENE-9450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384320#comment-17384320
]
Michael McCandless commented on LUCENE-9450:
--------------------------------------------
Catching up here...
So yeah as things stand, we force users of taxonomy faceting to fully reindex
on upgrade to 9.0, which is not a great option, but I really love that Lucene
is getting stricter enforcement of consistent field types with LUCENE-9334.
[~gworah] could we instead index the new {{BinaryDocValues}} form into a
different Lucene field? Then we could have graceful back compat (no reindexing
required) while also migrating to the more efficient {{BinaryDocValues}}
representation? It's OK to make this change pre-9.0 since we are allowed to
make breaking changes to Lucene's nightly/SNAPSHOT builds. But if this
approach can work, we should make this a blocker for 9.0.
> 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
