[
https://issues.apache.org/jira/browse/LUCENE-6572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653281#comment-16653281
]
Simon Willnauer commented on LUCENE-6572:
-----------------------------------------
> Another solution would be to remove the support for the parent/child query in
> highlighting. I don't see how this can be useful since the inner query
> explicitly targets a different set of documents (not the one returned in the
> top hits). If users really wants this feature the unified highlighter has a
> simple mechanism to rewrite custom queries that are not handled by the
> default implementation.
I am ok with this. this is a breaking change FWIW. [~martijn.v.groningen] do
you have background on why we have support for these queries in highlighting?
> 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
