[ 
https://issues.apache.org/jira/browse/LUCENE-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676754#action_12676754
 ] 

Michael McCandless commented on LUCENE-1500:
--------------------------------------------

bq. So to be consistent, where else in Lucene might an 
"IncorrectTokenOffsetsException" be a possibility - IndexWriter.addDocument(..)?

Good question!

I don't think we can throw it from addDocument, because we cannot
assume/assert that the int startOffset & endOffset are in fact
character offsets into the String/Reader we had been given?

Technically, to Lucene the start/end offsets are somewhat opaque (I
think?).  It's not until you actually do something with them (eg, call
the highlighter) that you are saying "these are really supposed to be
character offsets into the specific text I just provided you".


> 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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org

Reply via email to