[ https://issues.apache.org/jira/browse/SOLR-5623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868368#comment-13868368 ]
Benson Margulies commented on SOLR-5623: ---------------------------------------- Here's another ouch. Doc for Document#get says: {code} /** Returns the string value of the field with the given name if any exist in * this document, or null. If multiple fields exist with this name, this * method returns the first value added. If only binary fields with this name * exist, returns null. * For {@link IntField}, {@link LongField}, {@link * FloatField} and {@link DoubleField} it returns the string value of the number. If you want * the actual numeric field instance back, use {@link #getField}. */ {code} But given a Solr field like the following, with a value of '1', I end up with \u0080\u0000\u0001. It doesn't appear to be an IntField, just a Field. What am I missing? {code} <field name="id" type="sint" indexed="true" stored="true" multiValued="false"/> {code} > Better diagnosis of RuntimeExceptions in analysis > ------------------------------------------------- > > Key: SOLR-5623 > URL: https://issues.apache.org/jira/browse/SOLR-5623 > Project: Solr > Issue Type: Bug > Reporter: Benson Margulies > > 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