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

Mikhail Khludnev commented on SOLR-11251:
-----------------------------------------

I want to rephrase [the suggestion regarding 
debugging|https://lucene.apache.org/solr/guide/7_1/json-request-api.html#debugging].
bq. If you want to see what your merged/parsed JSON looks like, you can turn on 
debugging (debug=true), and it will come back under the "json" key along with 
the other debugging information.
This suggestion doesn't work on large indices, {{debug=true}} as well as 
{{debugQuery=true}} just never get back due to overall burden. The situation is 
even tricker since {{debug=query}} isn't propagated to slaves in the 
distributed search. The option I've found is {{debug=timing}}, which works like 
a charm but lacks of cluelessness. Should we put as just as 
bq. If you want to see what your merged/parsed JSON looks like, you can turn on 
debugging (debug=timing), and it will come back under the "json" key along with 
the other debugging information.     
Or also mention such caveat/explanations as well (which might be good for SEO 
reasons, btw).
bq. Note: that debug=true as well as debugQuery=true might have enormous impact 
on request time, and debug=true is ignored for json.facet.  

> Ref Guide: Add docs on JSON facet module
> ----------------------------------------
>
>                 Key: SOLR-11251
>                 URL: https://issues.apache.org/jira/browse/SOLR-11251
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: documentation, Facet Module
>            Reporter: Cassandra Targett
>            Assignee: Yonik Seeley
>            Priority: Major
>             Fix For: 7.2
>
>         Attachments: SOLR-11251.patch, faceted-search.adoc
>
>
> The old Confluence Ref Guide had a draft version of basic docs on JSON 
> facets, but it never made its way into the published guides. During the 
> conversion of the Ref Guide from Confluence, I made sure the page was 
> exported and converted to {{.adoc}} format.
> The doc was never updated after any of the changes that have been made to 
> JSON facet functionality since it was originally written, so it's possibly 
> inaccurate or just out of date. Someone could take a crack at finishing the 
> conversion cleanup and updating it with latest information so someday it can 
> be part of the published Guide.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to