[
https://issues.apache.org/jira/browse/SOLR-15356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325236#comment-17325236
]
David Smiley commented on SOLR-15356:
-------------------------------------
[~mayyas], Solr has a sort of utility component
UninvertDocValuesMergePolicyFactory (UDVMP) SOLR-10046 that can convert an
index that doesn't have docValues for certain fields to one that does. It
happens gradually during the course of index merges. Based on what I see in
LUCENE-9334, it seems UDVMP is fundamentally incompatible with Lucene 9
henceforth because Lucene can no longer accept differing FieldInfo values
across segments. WDYT? Do you think it may be possible to play tricks by
wrapping the LeafReader to pretend a segment has docValues when it didn't
actually?
CC [~cpoerschke] [~k317h]
> Lucene requires consistency across fields
> -----------------------------------------
>
> Key: SOLR-15356
> URL: https://issues.apache.org/jira/browse/SOLR-15356
> Project: Solr
> Issue Type: Task
> Components: Schema and Analysis
> Affects Versions: main (9.0)
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Blocker
>
> LUCENE-9334 requires more consistency across fields (Lucene 9). We must
> accommodate this in some tests which started failing. Example:
> org.apache.solr.index.UninvertDocValuesMergePolicyTest
> "cannot change field "string_add_dv_later" from doc values type=NONE to
> inconsistent doc values type=SORTED"
> From
> org.apache.lucene.index.FieldInfo.verifySameDocValuesType(FieldInfo.java:271)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
