[
https://issues.apache.org/jira/browse/SOLR-15356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325334#comment-17325334
]
Mayya Sharipova commented on SOLR-15356:
----------------------------------------
Indeed, it looks like UDVMP is incompatible with Lucene 9, as currently the
rule is that a first document containing a field sets up a unmodifiable field
schema (FieldInfo) for this field.
But we want to find some ways to relax this rule for older indices that contain
inconsistent field schemas across documents and segments. And I wonder if we
can also think of some special cases like yours that will allow these
inconsistencies even for new indices.
cc [~jpountz]
> 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]
