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

Uwe Schindler edited comment on LUCENE-7293 at 5/20/16 9:24 PM:
----------------------------------------------------------------

In addition the new dependency was not correctly added to the Maven POM + you 
changed dependnecies in a minor version upgrade - this is a no-go. So please, 
please - revert this and fix in a dyanmic way without a hard dependency just to 
check that something is not supported.


was (Author: thetaphi):
In addition the new dependency was not correctly added to the Maven POM. So 
please, please - revert this and fix in a dyanmic way without a hard dependency 
just to check that something is not supported.

> Highlighting with GeoPointInBBoxQuery can result in Exception
> -------------------------------------------------------------
>
>                 Key: LUCENE-7293
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7293
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: modules/highlighter
>    Affects Versions: 5.5, 6.0, master (7.0)
>            Reporter: britta weber
>             Fix For: 6.1, 6.0.1, master (7.0)
>
>         Attachments: LUCENE-7293.patch, LUCENE-7293.patch
>
>
> Highlighter and GeoPointInBBoxQuery don't play well together. I wrote a test 
> here that throws an exception which I think it should not:
> https://github.com/brwe/lucene-solr/commit/311f5527ffb6f3ef50e3f74b54456aa7b29d8898
> The problem seems to be that GeoPointInBBoxQuery calls rewrite with a reader 
> that contains a text field (which we want to highlight) and therefore has the 
> wrong encoding. 
> This is from an elasticsearch issue: 
> https://github.com/elastic/elasticsearch/issues/17537



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to