[jira] [Comment Edited] (SOLR-7672) introduce implicit _parent_:true

2019-01-28 Thread David Smiley (JIRA)


[ 
https://issues.apache.org/jira/browse/SOLR-7672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16754413#comment-16754413
 ] 

David Smiley edited comment on SOLR-7672 at 1/28/19 10:29 PM:
--

How so [~mkhludnev]?  I _wish_ it were so.  The recent improvements to nested 
docs in Solr have yet to touch the block join queries.  In 8.0, I think these 
query parsers could assume {{which:-\_nest_path_:*}} but only if this field is 
defined.  This approach is taken with the updated child doc transformer.


was (Author: dsmiley):
How so [~mkhludnev]?  I _wish_ it were so.  The recent improvements to nested 
docs in Solr have yet to touch the block join queries.  In 8.0, I think these 
query parsers could assume {{parent:-\_nest_path_:*}} but only if this field is 
defined.  This approach is taken with the updated child doc transformer.

> introduce implicit _parent_:true  
> --
>
> Key: SOLR-7672
> URL: https://issues.apache.org/jira/browse/SOLR-7672
> Project: Solr
>  Issue Type: Improvement
>  Components: query parsers, update
>Affects Versions: 5.2
>Reporter: Mikhail Khludnev
>Assignee: Mikhail Khludnev
>Priority: Major
>
> 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
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Comment Edited] (SOLR-7672) introduce implicit _parent_:true

2015-12-03 Thread Mikhail Khludnev (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-7672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15038213#comment-15038213
 ] 

Mikhail Khludnev edited comment on SOLR-7672 at 12/4/15 7:32 AM:
-

[~ysee...@gmail.com]
my turn: {{\_type_:_root_}} and spin off a jira about  
{{\_type_:\_root_.home_address}} or  {{\_type_:home_address}} 
Do you like it?


was (Author: mkhludnev):
[~ysee...@gmail.com]
my turn: {{_type_:_root_}} and spin off a jira about  
{{_type_:_root_.home_address}} or  {{_type_:home_address}} 
Do you like it?

> introduce implicit _parent_:true  
> --
>
> Key: SOLR-7672
> URL: https://issues.apache.org/jira/browse/SOLR-7672
> 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
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org