You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Yonik Seeley (JIRA)" <ji...@apache.org> on 2017/11/30 03:09:00 UTC
[jira] [Comment Edited] (SOLR-11706) JSON FacetModule can't compute
stats (min,max,etc...) on multivalued fields
[ https://issues.apache.org/jira/browse/SOLR-11706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16272091#comment-16272091 ]
Yonik Seeley edited comment on SOLR-11706 at 11/30/17 3:08 AM:
---------------------------------------------------------------
I was just trying to point out that it's a "yeah, that's not implemented yet" rather than "what the heck is wrong... I'll dig into it" situation.
bq. Well ... presumably, in the absence of any official documentation (yet)
Here's what we have so far:
https://builds.apache.org/view/L/view/Lucene/job/Solr-reference-guide-master/javadoc/json-facet-api.html#AggregationFunctions
bq. I'm not really following what your point about MinMaxAgg is.
If one goes about implementing support for avg(multivalued_field), then the first issue one will run up against is that the function parser will fail because of the generic value source check for single valued fields. min() and max() have already gotten around this issue, and I was pointing out how other stats could do the same thing.
bq. I'm not really sure what it would mean to "care about ... multi-valued functions" – AFAIK we've never had any multivalued functions? .. are you just hypothosising that maybe someday we could?
Yes, IMO we already need them. There are multiple ways to handle multi-valued fields and we don't support that well anywhere.
was (Author: yseeley@gmail.com):
I was just trying to point out that it's a "yeah, that's not implemented yet" rather than "what the heck is wrong... I'll dig into it" situation.
bq. Well ... presumably, in the absence of any official documentation (yet)
Here's what we have so far:
https://builds.apache.org/view/L/view/Lucene/job/Solr-reference-guide-master/javadoc/json-facet-api.html#AggregationFunctions
bq. I'm not really following what your point about MinMaxAgg is.
If one goes about implementing support for avg(multivalued_field), then the first issue one will run up against is that the function parser will fail because of the generic value source check for single valued fields. min() and max() have already gotten around this issue, and I was pointing out how other stats could do the same thing.
bq.
I'm not really sure what it would mean to "care about ... multi-valued functions" – AFAIK we've never had any multivalued functions? .. are you just hypothosising that maybe someday we could?
Yes, IMO we already need them. There are multiple ways to handle multi-valued fields and we don't support that well anywhere.
> JSON FacetModule can't compute stats (min,max,etc...) on multivalued fields
> ---------------------------------------------------------------------------
>
> Key: SOLR-11706
> URL: https://issues.apache.org/jira/browse/SOLR-11706
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Hoss Man
> Attachments: SOLR-11706.patch
>
>
> While trying to write some tests demonstrating equivalences between the StatsComponent and the JSON FacetModule i discovered that the FacetModules stat functions (min, max, etc...) don't seem to work on multivalued fields.
> Based on the stack traces, i gather the problem is because the FacetModule seems to rely exclusively on using the "Function" parsers to get a value source -- apparently w/o any other method of accumulating numeric stats from multivalued (numeric) DocValues?
--
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