[jira] [Comment Edited] (SOLR-10949) analytics component has hard coded assumptions about Trie numeric fields -- tests fail with randomized point fields

["Dennis Gove (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-10949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095580#comment-16095580 ] 

Dennis Gove edited comment on SOLR-10949 at 7/20/17 11:52 PM:
--------------------------------------------------------------

Assumptions about Trie numeric fields in the Analytics component has been resolved as part of SOLR-10123. That assumption is no longer being made.


was (Author: dpgove):
Assumptions abo

> 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
>              Labels: numeric-tries-to-points
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org