[
https://issues.apache.org/jira/browse/SOLR-13008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16748006#comment-16748006
]
Gus Heck commented on SOLR-13008:
---------------------------------
I'm wondering if it might be better to have this set on a per field basis i.e.
{{:[json indent=true]}}. That one stupidly large field might make you scroll
forever to find the field you actually want to read... This should in theory be
not too hard since IIRC these parse with the same code as LocalParams (just [
instead of { ) and other transformers have args (i.e. {{val}} and {{explain}})
> JSON Document Transformer doesn't heed "indent" parameter
> ---------------------------------------------------------
>
> Key: SOLR-13008
> URL: https://issues.apache.org/jira/browse/SOLR-13008
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Response Writers
> Affects Versions: 7.5
> Reporter: Eric Pugh
> Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> A query like "wt=json&fl=id,subject:[json]&indent=true", will return the
> field subject as JSON, however the indent parameter is ignored on the nested
> JSON. This can lead to a very wide response that you have to scroll over.
> Often I add indent=true becasue I want to see the structure of my embedded
> JSON text, and I need to cut'n'paste over to another editor. This would let
> the nested JSON object be pretty printed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
