[
https://issues.apache.org/jira/browse/SOLR-15356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325485#comment-17325485
]
David Smiley commented on SOLR-15356:
-------------------------------------
org.apache.solr.client.solrj.SolrExampleXMLTest.testUpdateField:
Interestingly, this new Lucene setting exposed two bugs I discovered in
CurrencyFieldType – SOLR-15357 & SOLR-15358. The test isn't trying to actually
test CurrencyFieldType either; it's a copyField internal detail that's
circumstantial -- our schemas are kitchen-sinks of miscellaneous stuff ("price"
\-> "price_c"). Changing this test to use the dynamic field name "price_f" (a
float) side-steps those bugs. I'll dig more tomorrow.
> 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]
