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

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

bq. What did you think of my suggestion to fix this problem at it's source - 
i.e. Token should never be in a state with end<start in the first place?

I'm wary of this, for the same reason as cited above.  I think the
start/end offsets are rather opaque to Lucene, and I would lean
towards asserting as little as possible about them during indexing.

(Not to mention the challenges, as you enumerated, of actually doing
this checking with the current API).

I think at point-of-use (highlighting) we should assert the offsets
are valid, for highlighting.


> 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.9
>
>         Attachments: Lucene-1500-NewException.patch, 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