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

Grant Ingersoll commented on SOLR-1622:
---------------------------------------

Some notes from IRC:
-cool - if you go into the stats stuff, dump the silly string based numerics 
(that we had to do in the past) and also make it per-segment 
- we need one capability in the lucene FieldCache, and we could dump the legacy 
"SortedInt" stuff for good
-that's simply the ability to tell of a document had a value or not

> Add aggregate Math capabilities to Solr above and beyond the StatsComponent
> ---------------------------------------------------------------------------
>
>                 Key: SOLR-1622
>                 URL: https://issues.apache.org/jira/browse/SOLR-1622
>             Project: Solr
>          Issue Type: New Feature
>          Components: search
>            Reporter: Grant Ingersoll
>            Priority: Minor
>
> It would be really cool if we could have a QueryComponent that enabled doing 
> aggregating calculations on search results similar to what the StatsComponent 
> does, but in a more generic way.
> I also think it makes sense to reuse some of the function query capabilities 
> (like the parser, etc.).
> I imagine the interface might look like:
> {code}
> math=true&func=recip(sum(A))
> {code}
> This would calculate the reciprocal of the sum of the values in the field A.  
> Then, you could do go across fields, too
> {code}
> math=true&func=recip(sum(A, B, C))
> {code}
> Which would  sum the values across fields A, B and C.
> It is important to make the functions pluggable and reusable.  Might be also 
> nice to see if we can share the core calculations between function queries 
> and this capability such that if someone adds a new aggregating function, it 
> can also be used as a new Function query.
> Of course, we'd want plugin functions, too, so that people can plugin their 
> own functions.  After this is implemented, I think StatsComponent becomes a 
> derivative of the new MathComponent.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to