lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vadim Kirilchuk (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4768) Child Traversable To Parent Block Join Query
Date Mon, 11 Feb 2013 15:37:13 GMT


Vadim Kirilchuk commented on LUCENE-4768:

Ok, let me tell you: 
i have a search phrase "Saturn Sky Blue Sedan"
i have model "Saturn Sky" with trim color:"Blue", bodyStyle:"Sedan"
also i have model "Saturn Astra" with trim color:"Sky Blue", bodyStyle: "Sedan"

The result that i expect is result of following query 
result = Saturn AND ((Sky AND ((Blue AND Sedan) OR 'Blue Sedan')) OR ('Sky Blue' AND Sedan)
OR 'Sky Blue Sedan' ) 
    OR ('Saturn Sky' AND ((Blue AND Sedan) OR 'Blue Sedan') OR ('Saturn Sky Blue' AND Sedan)
OR ('Saturn Sky Blue Sedan')
wow..this query tree grows very fast =)

i am trying to achieve the same result but without using complex query with a post constraint
that can verify that matched terms can cover my phrase.
So, if i have matched 'Sky Blue' and 'Sedan' in my child or if i have matched 'Sky' and 'Blue'
and 'Sedan' in my child i can check with my post constraint that i actually got a match for
the phrase. 

To accomplish this task i need to know field and text of each matched leaf scorer. This is
not about scoring..

> Child Traversable To Parent Block Join Query
> --------------------------------------------
>                 Key: LUCENE-4768
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/query/scoring
>         Environment: trunk
> git rev-parse HEAD
> 5cc88eaa41eb66236a0d4203cc81f1eed97c9a41
>            Reporter: Vadim Kirilchuk
>         Attachments: LUCENE-4768-draft.patch
> Hi everyone!
> Let me describe what i am trying to do:
> I have hierarchical documents ('car model' as parent, 'trim' as child) and use block
join queries to retrieve them. However, i am not happy with current behavior of ToParentBlockJoinQuery
which goes through all parent childs during nextDoc call (accumulating scores and freqs).
> Consider the following example, you have a query with a custom post condition on top
of such bjq: and during post condition you traverse scorers tree (doc-at-time) and want to
manually push child scorers of bjq one by one until condition passes or current parent have
no more childs.
> I am attaching the patch with query(and some tests) similar to ToParentBlockJoin but
with an ability to traverse childs. (i have to do weird instance of check and cast inside
my code) This is a draft only and i will be glad to hear if someone need it or to hear how
we can improve it. 
> P.s i believe that proposed query is more generic (low level) than ToParentBJQ and ToParentBJQ
can be extended from it and call nextChild() internally during nextDoc().
> Also, i think that the problem of traversing hierarchical documents is more complex as
lucene have only nextDoc API. What do you think about making api more hierarchy aware? One
level document is a special case of multi level document but not vice versa. WDYT?
> Thanks in advance.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message