[
https://issues.apache.org/jira/browse/SOLR-9026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264235#comment-15264235
]
Michael Sun commented on SOLR-9026:
-----------------------------------
Thanks [[email protected]] for reviewing. Here is my thoughts.
bq. "facet-trace" is the same name used for JSON Facet API, right? If both
faceting components are used at the same time, does this work?
That's good point. Let me separate them.
bq. it seems like one would really want elapsed time per facet.field (i.e
per-sub-facet)?
I think so, particularly when the query has multiple field faceting, it's good
to know which field faceting causes problem.
> Design Facet Telemetry for non-JSON field facet
> -----------------------------------------------
>
> Key: SOLR-9026
> URL: https://issues.apache.org/jira/browse/SOLR-9026
> Project: Solr
> Issue Type: Sub-task
> Components: Facet Module
> Reporter: Michael Sun
> Fix For: master
>
> Attachments: SOLR-9026.patch
>
>
> Non-JSON facet is widely used and telemetry is helpful is diagnosing
> expensive queries. As first step, the JIRA is to design telemetry for field
> facet.
> Example: (using films)
> {code}
> $curl
> 'http://localhost:8228/solr/films/select?debugQuery=true&facet.field=genre&facet.field=directed_by&facet=true&indent=on&q=*:*&wt=json'
> ...
> "facet-trace":{
> "elapse":1,
> "sub-facet":[{
> "processor":"SimpleFacets",
> "elapse":1,
> "action":"field facet",
> "maxThreads":0,
> "sub-facet":[{
> "method":"FC",
> "inputDocSetSize":1100,
> "field":"genre",
> "numBuckets":213},
> {
> "method":"FC",
> "inputDocSetSize":1100,
> "field":"directed_by",
> "numBuckets":1053}]}]},
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
