lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] [Commented] (SOLR-7672) introduce implicit _parent_:true
Date Fri, 04 Dec 2015 01:22:10 GMT


Yonik Seeley commented on SOLR-7672:

Yeah, that probably works.
We can always just use some syntactic sugar if we don't want a literal \_root\_ mandated in
whatever future query syntax we come up with.

Note to new readers: when you see italicized text, we normally don't mean it that way... it's
JIRA markup.  Normally what we really mean is a literal leading and trailing underscore on
whatever is being proposed.
{code}_type_:_root_ is what is being proposed here.{code}
And if you see backslashes in front of the underscores, you're probably reading the post in
raw form (i.e. from an email) and it means that the author is just trying to get JIRA to display
literal underscores (but not backslashes).

> introduce implicit _parent_:true  
> ----------------------------------
>                 Key: SOLR-7672
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: query parsers, update
>    Affects Versions: 5.2
>            Reporter: Mikhail Khludnev
>            Assignee: Mikhail Khludnev
>             Fix For: 5.4, Trunk
> Solr provides block join support in non-invasive manner. It turns out, it gives a chance
to shoot a leg. As it was advised by [~thetaphi] at SOLR-7606, let AddUpdateCommand add _parent_:true
field to the document (not to children). Do it *always* no matter whether it has children
or not.    
> Also, introduce default values for for block join qparsers \{!parent *which=\_parent\_:true*}
\{!child *of=\_parent\_:true*} (sometimes, I rather want to hide them from the user, because
they are misunderstood quite often).  
> Please share your concerns and vote.

This message was sent by Atlassian JIRA

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

View raw message