[
https://issues.apache.org/jira/browse/SOLR-7472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-7472:
---------------------------------
Attachment: SOLR-7472.patch
Patch with fix
> SortingResponseWriter does not log fl parameters that don't exist.
> ------------------------------------------------------------------
>
> Key: SOLR-7472
> URL: https://issues.apache.org/jira/browse/SOLR-7472
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.9, 4.9.1, 4.10, 4.10.1, 4.10.2, 4.10.4, 5.0, 5.1
> Reporter: Joel Bernstein
> Fix For: 5.2
>
> Attachments: SOLR-7472.patch
>
>
> The SortingResponseWriter, which is the response writer for the /export
> handler, does not log the error that is thrown when an fl is specified that
> does not exist.
> The reason for this is that an unchecked SolrException is being thrown from
> the IndexSchema. All other exceptions in SortingResponseWriter are wrapped in
> an IOException.
> For reasons I'm not entirely sure of the ResponseUtils class doesn't log the
> stacktrace for errors with codes between 500 and 100. It considers these to
> be normal error conditions. So the unchecked SolrException was not being
> logged.
> The short term fix for this is to catch the exception from the IndexSchema
> and wrap it in a IOException like the other exceptions from the
> SortingResponseWriter.
> Longer term I think it makes sense to review the ResponseUtil exception
> logging logic.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
