[ 
https://issues.apache.org/jira/browse/SOLR-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve McKay updated SOLR-4214:
------------------------------

    Attachment: stats.patch

The primary new feature is hierarchical faceting, e.g. facet by vendor and then 
facet each vendor by year. I've also added stats.sort, stats.limit, and 
stats.offset field params. stats.sort syntax is 
<sum|min|max|stdDev|average|sumOfSquares|count|missing|value>:<asc|desc> and 
limit and offset work as in SQL. Faceting will generally use more RAM and be 
faster than the 4.0 baseline. I've changed more than some might consider to be 
strictly necessary; this is because a large part of my effort has been to make 
faceting performant under adverse conditions, with large result sets and 
faceting on fields with large (1m+) cardinalities.

One caveat: distributed stats are broken in this patch due to other work in 
progress. Tests pass, although I changed a few test cases relating to what 
happens when stats.field is completely absent in the result set. The existing 
behavior is to return null as the stats result and my code returns zeroed-out 
stats, which IMO is more felicitous anyway.

The attached patch is diffed from branches/lucene_solr_4_0.

                
> Hierarchical stats
> ------------------
>
>                 Key: SOLR-4214
>                 URL: https://issues.apache.org/jira/browse/SOLR-4214
>             Project: Solr
>          Issue Type: New Feature
>          Components: SearchComponents - other
>            Reporter: Steve McKay
>         Attachments: stats.patch
>
>
> Hierarchical stats faceting, e.g. facet by vemdor and then facet each vendor 
> by year.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to