[
https://issues.apache.org/jira/browse/LUCENE-7293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler reopened LUCENE-7293:
-----------------------------------
Hi,
I reopening this, because I have a problem in let the whole highlighting module
depend on the spatial module, just to check that something is not a query.
I'd suggest to do a more dynamic check (e.g. compare string class name or
similar). If we also need to match subclasses, I'd suggest to try to
Class.forName the spatial class and use Class.isAssignableFrom, if found.
If you revert and fix the issue, please also don't forget to revert the
benchmark module's changes.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
