[SOLR-7472] SortingResponseWriter does not log fl parameters that don't exist.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.9, 4.9.1, 4.10, 4.10.1, 4.10.2, 4.10.4, 5.0, 5.1
• Fix Version/s: 5.2
• Assignee: Joel Bernstein
• Reporter: Joel Bernstein
• Created: 25/Apr/15 15:11
• Updated: 08/Oct/19 14:51
• Resolved: 15/May/15 18:43

Description

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.

Issue Links

• relates to: SOLR-7441 Improve overall robustness of the Streaming stack: Streaming API, Streaming Expressions, Parallel SQL