Hi SOLR Community,
Still hoping for help on this. Is there anyone out there who understands
child docs well enough to answer the question of "yes this should work" or
"no it cannot work"?
Thanks,
Stephen
On Wed, Oct 27, 2021 at 8:51 AM Stephen Lewis Bianamara <
stephen.bianam...@gmail.com> wrote:
> Hi Folks,
>
> Wanted to follow up here. Can someone help me just answer whether what I'm
> hoping for is feasible?
>
> (a) The desired outcome is supported with the right model/queries
> (b) The desired outcome is not supported; maybe it could be in the future
> (c) The desired outcome is fundamentally unsupportable for the
> foreseeable future
>
> To summarize, the desired behavior is:
>
> - Query which can AND across child docs (i.e, return parents whos children
> match an AND query even if tokens are spread across children)
> - Query whose parents are returned based on relevance of the children
>
> In my example, obviously there is parent data being queried ("post_en"),
> but the parent data could easily be made child data if need be.
>
> Thanks!
> Stephen
>
> On Mon, Oct 25, 2021 at 6:54 AM Stephen Lewis Bianamara <
> stephen.bianam...@gmail.com> wrote:
>
>> Hi SOLR Community,
>>
>> I'm experimenting with solr 8.10 and trying to get a query pattern with
>> child docs to work. An example of a nested document structure I'd like to
>> search is below. In this example, there will only be two levels, child of
>> type:post and /comments children.
>> {
>> "id": "post1",
>> "type": "post",
>> "post_en": "I put lemon on my apple slices to keep them fresh",
>> "comments": [
>> {
>> "id": "comment1",
>> "type": "comment",
>> "comment_en": "Lime works too"
>> },
>> {
>> "id": "comment2",
>> "type": "comment",
>> "comment_en": "Does it work for pears?"
>> }
>> ]
>> }
>>
>> What I'd like is to be able to do keyword search for /lemon apple/ and
>> only return the parent; /lemon lime/ and return the parent and comment1;
>> /lemon pear/ and return the parent and comment2; /lime pear/ and return the
>> parent, comment1, and comment2. And /lime gum/ should return nothing (as if
>> it were an AND query). Additionally, this should all be done with relevance.
>>
>> I've tried a few combinations of nested docs from this documentation
>> ,
>> but am having trouble getting this to work. I wonder if I'm asking more
>> from block join/child doc transformer than it currently supports, or
>> perhaps I'm just missing something. Can someone familiar with nesting
>> documents help me out? I've included my schema below as well.
>>
>> Thanks!
>> Stephen
>>
>>
>>
>>
>>
>> > omitNorms="true" />
>>
>>
>>
>>
>> > docValues="false" />
>>
>> > stored="true" />
>>
>> id
>>
>>
>>
>> > />
>> > positionIncrementGap="100" autoGeneratePhraseQueries="true">
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
