Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BB3D017B8B for ; Sat, 25 Apr 2015 15:12:39 +0000 (UTC) Received: (qmail 9745 invoked by uid 500); 25 Apr 2015 15:12:38 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 9670 invoked by uid 500); 25 Apr 2015 15:12:38 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 9657 invoked by uid 99); 25 Apr 2015 15:12:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 25 Apr 2015 15:12:38 +0000 Date: Sat, 25 Apr 2015 15:12:38 +0000 (UTC) From: "Joel Bernstein (JIRA)" To: dev@lucene.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (SOLR-7472) SortingResponseWriter does not log fl parameters that don't exist. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 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