Mikhail,
Actually, your suggestion worked! I was making a typo on the field name. Thank
you very much!
TK
p.s. I have found a mention of _query_ "magic field" in the Solr Reference Guide
On 7/8/18 11:04 AM, TK Solr wrote:
Thank you.
This is more promising because I see the second clause i
Thank you.
This is more promising because I see the second clause in parsedquery. But it is
hitting zero document.
The debug query output looks like this. explain is empty:
rawquerystring":"_query_:{!parent which=\"isParent:true\" v='attrname:genre AND
attrvalue:drama'} AND _query_:{!parent
agh... It's my pet peeve.
what about
q= {!parent which="isParent:true" v='attrname:genre AND attrvalue:drama'}
AND {!parent which="isParent:true" v='attrname:country AND attrvalue:USA'}
^leading space
q=_query_:{!parent which="isParent:true" v='attrname:genre AND
attrvalue:drama'} AND _query_:{!pa
Thank you, Mikhail. But this didn't work. The first {!parent which='...'
v='...'} alone works. But the second {!parent ...} clause is completely ignored.
In fact, if I turn on debugQuery, rawquerystring and querystring have the second
query but parsedquery and parsedquery_toString only have the f
Hello,
q={!parent which="isParent:true" v='attrname:genre AND attrvalue:drama'} AND
{!parent which="isParent:true" v='attrname:country AND attrvalue:USA'}
On Tue, Jul 3, 2018 at 3:35 PM TK Solr wrote:
> I have a document with child documents like:
>
>
> maindoc_121
> true
> c
