[
https://issues.apache.org/jira/browse/SOLR-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Molloy updated SOLR-4212:
-------------------------------
Description:
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.
was:
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
a query (per field) that would be intersected with DocSet used to calculate
pivot count, stored in separate q-count.
> 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.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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
