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

Hoss Man commented on SOLR-4212:
--------------------------------

I haven't had a chance to review this patch, but in response to a dev@lucene 
thread about it...

bq. Base idea is to have something like: 
{{facet.pivot=field1,field2,field3f.field2.facet.pivot.q=somequery&f.field3.facet.pivot.q=somedate:\[NOW-1YEAR
 TO NOW\]&f.field3.facet.pivot.q=someotherquery}} ... Which would add results 
similar to facet queries, at the appropriate level in the pivots.

>From a functionality standpoint, what you are setting out to do here seems 
>like a great idea -- but personally i think that syntax looks really 
>cumbersome?

>From a user API standpoint, It seems your gola here would gel really well with 
>the syntax i proposed in SOLR-6348/(SOLR-6351,SOLR-6352,SOLR-6353) if you 
>think about it in terms of "hanging query facets off of pivots" ... ie:

{noformat}
facet.pivot={!query=r1}category,manufacturer
facet.query={!tag=r1}somequery
facet.query={!tag=r1}somedate:[NOW-1YEAR TO NOW]
{noformat}

that seems like it might be cleaner, and fit better with some of the other 
ongoing work, what do you think?

> Support for facet pivot query for filtered count
> ------------------------------------------------
>
>                 Key: SOLR-4212
>                 URL: https://issues.apache.org/jira/browse/SOLR-4212
>             Project: Solr
>          Issue Type: Improvement
>          Components: search
>    Affects Versions: 4.0
>            Reporter: Steve Molloy
>             Fix For: 4.9, Trunk
>
>         Attachments: SOLR-4212-multiple-q.patch, SOLR-4212-multiple-q.patch, 
> SOLR-4212.patch, SOLR-4212.patch, SOLR-4212.patch, patch-4212.txt
>
>
> Facet pivot provide hierarchical support for computing data used to populate 
> a treemap or similar visualization. TreeMaps usually offer users extra 
> information by applying an overlay color on top of the existing square sizes 
> based on hierarchical counts. This second count is based on user choices, 
> representing, usually with gradient, the proportion of the square that fits 
> the user's choices.
> The proposition is to add a facet.pivot.q parameter that would allow to 
> specify one or more queries (per field) that would be intersected with DocSet 
> used to calculate pivot count, stored in separate qcounts list, each entry 
> keyed by the query.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to