[
https://issues.apache.org/jira/browse/LUCENE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676648#action_12676648
]
Peter Wolanin commented on LUCENE-1500:
---------------------------------------
Yes - this patch is not a fix - but a work-around.
The root cause is clearly somewhere in the code generating the token stream -
tokens seem to be getting positions in bytes rather than characters.
DefaultSolrHighlighter.java has this code:
{code}
import org.apache.lucene.search.highlight.TokenSources;
...
// create TokenStream
try {
// attempt term vectors
if( tots == null )
tots = new TermOffsetsTokenStream(
TokenSources.getTokenStream(searcher.getReader(), docId, fieldName) );
tstream = tots.getMultiValuedTokenStream( docTexts[j].length() );
}
catch (IllegalArgumentException e) {
// fall back to anaylzer
tstream = new
TokenOrderingFilter(schema.getAnalyzer().tokenStream(fieldName, new
StringReader(docTexts[j])), 10);
}
{code}
> Highlighter throws StringIndexOutOfBoundsException
> --------------------------------------------------
>
> Key: LUCENE-1500
> URL: https://issues.apache.org/jira/browse/LUCENE-1500
> Project: Lucene - Java
> Issue Type: Bug
> Components: contrib/highlighter
> Affects Versions: 2.4
> Environment: Found this running the example code in Solr (latest
> version).
> Reporter: David Bowen
> Assignee: Michael McCandless
> Fix For: 2.4.1, 2.9
>
> Attachments: LUCENE-1500.patch, patch.txt
>
>
> Using the canonical Solr example (ant run-example) I added this document
> (using exampledocs/post.sh):
> <add><doc>
> <field name="id">Test for Highlighting
> StringIndexOutOfBoundsExcdption</field>
> <field name="name">Some Name</field>
> <field name="manu">Acme, Inc.</field>
> <field name="features">Description of the features, mentioning various
> things</field>
> <field name="features">Features also is multivalued</field>
> <field name="popularity">6</field>
> <field name="inStock">true</field>
> </doc></add>
> and then the URL
> http://localhost:8983/solr/select/?q=features&hl=true&hl.fl=features caused
> the exception.
> I have a patch. I don't know if it is completely correct, but it avoids this
> exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
