[ https://issues.apache.org/jira/browse/SOLR-5623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shalin Shekhar Mangar updated SOLR-5623: ---------------------------------------- Attachment: SOLR-5623-nowrap.patch The change to DirectUpdateHandler2 broke some tests because now it wraps a SolrException again in another SolrException and some tests were expecting the exception's cause to be the real cause. The attached patch only wraps the RuntimeException if they're not SolrException. Thoughts? > Better diagnosis of RuntimeExceptions in analysis > ------------------------------------------------- > > Key: SOLR-5623 > URL: https://issues.apache.org/jira/browse/SOLR-5623 > Project: Solr > Issue Type: Bug > Affects Versions: 4.6.1 > Reporter: Benson Margulies > Assignee: Benson Margulies > Fix For: 5.0, 4.7 > > Attachments: SOLR-5623-nowrap.patch > > > If an analysis component (tokenizer, filter, etc) gets really into a hissy > fit and throws a RuntimeException, the resulting log traffic is less than > informative, lacking any pointer to the doc under discussion (in the doc > case). It would be more better if there was a catch/try shortstop that logged > this more informatively. -- This message was sent by Atlassian JIRA (v6.1.5#6160) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org