[
https://issues.apache.org/jira/browse/SOLR-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14368940#comment-14368940
]
Steve Molloy commented on SOLR-6663:
------------------------------------
+1 This seems straight-foward and flexible enough for every case I can think
of. Also agree with the single tag name case to preserve current behaviour.
> decide rules & syntax for computing stats/ranges/queries only at certain
> levels of a pivot
> ------------------------------------------------------------------------------------------
>
> Key: SOLR-6663
> URL: https://issues.apache.org/jira/browse/SOLR-6663
> Project: Solr
> Issue Type: Sub-task
> Reporter: Hoss Man
>
> [~smolloy] asked a great question in SOLR-6351...
> bq. One more question around this, which applies for SOLR-6353 and SOLR-4212
> as well. Should we have a syntax to apply stats/queries/ranges only at
> specific levels in the pivot hierarchy? It would reduce amount of computation
> and size of response for cases where you only need it at a specific level
> (usually last level I guess).
> I'm splitting this off into it's own Sub-task for further discussion.
> ----
> For now, the "stats" localparam must be a single tag, and the "work around"
> is to add a common tag to all stats you want to use.
> ie, this will cause an error...
> {noformat}
> stats.field={!tag=tagA}price
> stats.field={!tag=tagB}popularity
> stats.field={!tag=tagB}clicks
> facet.pivot={!stats=tagA,tagB}xxx,yyy,zz
> {noformat}
> but this will work...
> {noformat}
> stats.field={!tag=tagA,tagPivot}price
> stats.field={!tag=tagB,tagPivot}popularity
> stats.field={!tag=tagB,tagPivot}clicks
> facet.pivot={!stats=tagPivot}xxx,yyy,zz
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
