You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Joel Bernstein (JIRA)" <ji...@apache.org> on 2015/04/25 17:12:38 UTC

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

Joel Bernstein created SOLR-7472:
------------------------------------

             Summary: 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: 5.1, 5.0, 4.10.4, 4.10.2, 4.10.1, 4.10, 4.9.1, 4.9
            Reporter: Joel Bernstein
             Fix For: 5.2


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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org