[
https://issues.apache.org/jira/browse/SOLR-10807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16039949#comment-16039949
]
Hoss Man commented on SOLR-10807:
---------------------------------
Been reviewing some of these issues to try and wrap my head around the current
problems so i can keep them in mind when looking for the best way to move
forward with total randomization of trie vs points. Here's what i've got so
far...
* SOLR-10834 tracks the broader problem of test schemas using TrieFooFields for
uniqueKey
* SOLR-10830 (w/ SOLR-10829) is the root cause of the PeerSyncTest failure
* SOLR-10832 is the root cause of the CdcrBootstrapTest failure
* SOLR-10833 is the root cause of all the failures realted to
NumberFormatException on bad input (TestCloudDeleteByQuery, etc...)
* SpatialPointVectorFieldType is deprecated with the plan to remove it in 8.0
(see SOLR-10729)
** so that seems like a candidate for leaving one explicit {{TrieDoubleField}}
in {{schema-spatial.xml}}
* SOLR-10835 tracks ExportWriter explicitly rejecting non-Trie fields
> Randomize PointFields in all tests unless explicit reason not to
> -----------------------------------------------------------------
>
> Key: SOLR-10807
> URL: https://issues.apache.org/jira/browse/SOLR-10807
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Hoss Man
> Assignee: Hoss Man
> Priority: Blocker
> Fix For: master (7.0)
>
> Attachments:
> core.test.log.fde06f34b7f9d0916a134b3efaa8780892ff8e39.txt, core.test.log.txt
>
>
> We need to seriously beef up our testing of PointFields to figure out what
> Solr features don't currently work with PointFields.
> The existing Trie/Point randomization logic in SolrTestCaseJ4 is a good start
> -- but only a handful of schema files leverage it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
