[
https://issues.apache.org/jira/browse/SOLR-10949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064021#comment-16064021
]
ASF subversion and git services commented on SOLR-10949:
--------------------------------------------------------
Commit 9f56698d33d1db9fab6a0d6f63b360b334f71583 in lucene-solr's branch
refs/heads/master from Chris Hostetter
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=9f56698 ]
SOLR-10948: Fix extraction component to treat DatePointField the same as
TrieDateField
SOLR-10947: Randomize the usage of Points based numerics in contrib test schemas
This commit also adds @SuppressPointFields needed for SOLR-10949
> analytics component has hard coded assumptions about Trie numeric fields --
> tests fail with randomized point fields
> -------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-10949
> URL: https://issues.apache.org/jira/browse/SOLR-10949
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Hoss Man
>
> Found as part of SOLR-10947... attempting to use numeric PointFields in
> contrib/analytics tests cause problems in some tests due to classes like
> StatsCollectorSupplierFactory, RangeEndpointCalculator, and AnalyticsParsers
> having hard coded assumptions about using Trie based numeric fields (via
> instanceof and clas equality checks)
> (It's not immediately obvious if replacing these checks with inspection of
> {{FieldType.getNumberType()}} would solve all the problems, or if other
> assumptions are made down stream in the code)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
