[
https://issues.apache.org/jira/browse/SOLR-13008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701991#comment-16701991
]
Eric Pugh commented on SOLR-13008:
----------------------------------
Thanks [~elyograg] for looking at this. I was thinking as I worked on the
patch, of also expanding the documentation. It's a really powerful feature
that isn't well known! Do you think that should be a separate SOLR issue, or
add additional documentation, including the `indent=true` impact as part of
this issue?
As far as the precommit, I did get the error you suspected. So I added the
SHA checksum file. However, reading through the
`./solr/licenses/README.committers.txt` file, it appears I should add a
`jackson-dataformat-xml-LICENSE-ASL.txt` and an empty
`jackson-dataformat-xml-NOTICE.txt` file? Or is adding that the
responsibility of the commiter who actually commits this patch?
> 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: [email protected]
For additional commands, e-mail: [email protected]
