ted documents
You could do:
*) LinkedIn
*) Wiki
*) Write it up, give it to me and I'll stick it as a guest post on my blog
(with attribution of your choice)
*) Write it up, give it to Lucidworks and they may (not sure about
rules) stick it on their blog
Regards,
Alex.
http://
d be more than happy to. What goes around comes around!
>
> -Original Message-
> From: Alexandre Rafalovitch [mailto:arafa...@gmail.com]
> Sent: 21 November 2016 13:01
> To: solr-user
> Subject: Re: Combined Dismax and Block Join Scoring on nested documents
>
> A blog a
ovitch [mailto:arafa...@gmail.com]
Sent: 21 November 2016 13:01
To: solr-user
Subject: Re: Combined Dismax and Block Join Scoring on nested documents
A blog article about what you learned would be very welcome. These edge cases
are something other people could certainly learn from.
Share the knowledge f
> -Original Message-
> From: Mikhail Khludnev [mailto:m...@apache.org]
> Sent: 18 November 2016 12:58
> To: solr-user
> Subject: Re: Combined Dismax and Block Join Scoring on nested documents
>
> Hello Mike,
> Structured queries in Solr are way cumbersome.
> Start from:
&g
ember 2016 12:58
To: solr-user
Subject: Re: Combined Dismax and Block Join Scoring on nested documents
Hello Mike,
Structured queries in Solr are way cumbersome.
Start from:
q=+{!dismax v="skirt" qf="name"} +{!parent which=content_type:product score=min
v=childq}&childq=+i
Hello Mike,
Structured queries in Solr are way cumbersome.
Start from:
q=+{!dismax v="skirt" qf="name"} +{!parent which=content_type:product
score=min v=childq}&childq=+in_stock:true^=0 {!func}list_price_gbp&...
beside of "explain" there is a parsed query entry in debug that's more
useful for trou
