You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Yonik Seeley (JIRA)" <ji...@apache.org> on 2018/06/15 14:36:11 UTC
[jira] [Commented] (LUCENE-8359) Extend ToParentBlockJoinQuery with
'minimum matched children' functionality
[ https://issues.apache.org/jira/browse/LUCENE-8359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16513889#comment-16513889 ]
Yonik Seeley commented on LUCENE-8359:
--------------------------------------
I haven't had a chance to look at the patch, but +1 for the idea of adding the high level functionality!
> Extend ToParentBlockJoinQuery with 'minimum matched children' functionality
> ----------------------------------------------------------------------------
>
> Key: LUCENE-8359
> URL: https://issues.apache.org/jira/browse/LUCENE-8359
> Project: Lucene - Core
> Issue Type: New Feature
> Reporter: Andrey Kudryavtsev
> Priority: Minor
> Labels: lucene
> Attachments: LUCENE-8359
>
>
> I have a hierarchal data in index and requirements like 'match parent only if at least {{n}} his children were matched'.
> I used to solve it by combination of some lucene / solr tricks like 'frange' filtration by sum of matched children score, so it's doable out of the box with some efforts right now. But also it could be solved by \{{ToParentBlockJoinQuery}} extension with new numeric parameter, tried to do it in attached patch.
> Not sure if this should be in main branch, just put it here, maybe someone would have similar problems.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org