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

Martijn van Groningen commented on LUCENE-6572:
-----------------------------------------------

> do you have background on why we have support for these queries in 
>highlighting?

I don't recall why, but like the in comment you mention, it is weird to support 
this. A different highlight query should used for when child or parent 
documents need to be highlighed. Elasticsearch ignores parent/child queries 
when highlighting and expects that when users want highlighting for child docs 
that a highlight query should be specified.

> Highlighter depends on analyzers-common
> ---------------------------------------
>
>                 Key: LUCENE-6572
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6572
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: modules/highlighter
>            Reporter: Robert Muir
>            Assignee: Simon Willnauer
>            Priority: Blocker
>         Attachments: LUCENE-6572.patch, LUCENE-6572.patch
>
>
> This is a huge WTF, just for "LimitTokenOffsetFilter" which is only useful 
> for highlighting.
> Adding all these intermodule dependencies makes things too hard to use.
> This is a 5.3 release blocker.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to