[
https://issues.apache.org/jira/browse/SOLR-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046370#comment-13046370
]
Tommaso Teofili commented on SOLR-2582:
---------------------------------------
A possible fix which still allows an easy debug could be to get the "logging
field" property on processor initialization, then if that was not configured
it's possible to get the uniquekey from the SolrCore passed in the initialize()
method :
String logFieldName = solrUIMAConfiguration.getLogField()!= null ?
solrUIMAConfiguration.getLogField() :
solrCore.getSchema().getUniqueKeyField().getName();
> UIMAUpdateRequestProcessor error handling with small texts
> ----------------------------------------------------------
>
> Key: SOLR-2582
> URL: https://issues.apache.org/jira/browse/SOLR-2582
> Project: Solr
> Issue Type: Bug
> Affects Versions: 3.2
> Reporter: Tommaso Teofili
> Fix For: 3.3
>
>
> In UIMAUpdateRequestProcessor the catch block in processAdd() method can have
> a StringIndexOutOfBoundsException while composing the error message if the
> logging field is not set and the text being processed is shorter than 100
> chars (...append(text.substring(0, 100))...).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
