[ https://issues.apache.org/jira/browse/SOLR-8576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109784#comment-15109784 ]
Mark Miller commented on SOLR-8576: ----------------------------------- These things used to be handled here: {noformat} } catch (Exception e) { String collName = message.getStr("collection"); if (collName == null) collName = message.getStr(NAME); if (collName == null) { SolrException.log(log, "Operation " + operation + " failed", e); } else { SolrException.log(log, "Collection: " + collName + " operation: " + operation + " failed", e); } results.add("Operation " + operation + " caused exception:", e); SimpleOrderedMap nl = new SimpleOrderedMap(); nl.add("msg", e.getMessage()); nl.add("rspCode", e instanceof SolrException ? ((SolrException)e).code() : -1); results.add("exception", nl); } {noformat} > Collection API validation errors will simply be logged and the client will > get an error about the response timing out. > ---------------------------------------------------------------------------------------------------------------------- > > Key: SOLR-8576 > URL: https://issues.apache.org/jira/browse/SOLR-8576 > Project: Solr > Issue Type: Bug > Reporter: Mark Miller > > Perhaps introduced in SOLR-5681? > We need some tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org