[
https://issues.apache.org/jira/browse/SOLR-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004521#comment-15004521
]
Michael Sun commented on SOLR-8230:
-----------------------------------
Uploaded first patch for review. It adds a facet trace field in response to
reveal the debugging information of facet if debugQuery=true in request. Here
is some thoughts for the patch.
1. In the patch, it shows the facet processor used, elapse time and facet
description for each step to execute facet. If there is sub-facet, it shows the
facet hierarchy as well. It helps to understand how the facet is executed and
the cost of each step.
2. The total count and unique count is not included and is planned for next
sub-task.
3. The debug information is stored along with FacetContext since FacetContext
maintains steps and hierarchy of facet execution. FacetContext is organized in
a tree structure. The root of the tree is stored in ResponseBuilder as
"FacetContext".
4. FacetDebugInfo.getFacetDebugInfoInJSON() is designed to be static. The
reason is FacetContext is package private. From DebugComponent.java, there is
no good way to access facet debug information.
5. The escape string in JSON output format in facet trace in the response is
somehow not completely correct. I am trying to figure it out.
> Create Facet Telemetry for Nested Facet Query
> ---------------------------------------------
>
> Key: SOLR-8230
> URL: https://issues.apache.org/jira/browse/SOLR-8230
> Project: Solr
> Issue Type: Sub-task
> Components: Facet Module
> Reporter: Michael Sun
> Fix For: Trunk
>
> Attachments: SOLR-8230.patch
>
>
> This is the first step for SOLR-8228 Facet Telemetry. It's going to implement
> the telemetry for a nested facet query and put the information obtained in
> debug field in response.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
