Re: fq behavior...

[Bastien Latard - MDPI AG]

Thank you guys!
I got it.

kr,
Bast


On 06/05/2016 17:27, Erick Erickson wrote:

>From Yonik's blog:
"By default, Solr resolves all of the filters before the main query"

By definition, the non-cached fq clause _must_ be
executed over the entire data set in order to be
cached. Otherwise, how could the next query
that uses an identical fq clause make use of the
cached value?

If cache=false, it's  a different story as per Yonik's
blog.

On Fri, May 6, 2016 at 7:25 AM, Shawn Heisey  wrote:

On 5/6/2016 12:07 AM, Bastien Latard - MDPI AG wrote:

Thank you Susmit, so the answer is:
fq queries are by default run before the main query.

Queries in fq parameters are normally executed in parallel with the main
query, unless they are a postfilter.  I am not sure that the standard
parser supports being run as a postfilter.  Some parsers (like geofilt)
do support that.

Susmit already gave you this link where some of that is explained:

http://yonik.com/advanced-filter-caching-in-solr/

Thanks,
Shawn



Kind regards,
Bastien Latard
Web engineer
--
MDPI AG
Postfach, CH-4005 Basel, Switzerland
Office: Klybeckstrasse 64, CH-4057
Tel. +41 61 683 77 35
Fax: +41 61 302 89 18
E-mail:
lat...@mdpi.com
http://www.mdpi.com/

Re: fq behavior...

[Erick Erickson]

>From Yonik's blog:
"By default, Solr resolves all of the filters before the main query"

By definition, the non-cached fq clause _must_ be
executed over the entire data set in order to be
cached. Otherwise, how could the next query
that uses an identical fq clause make use of the
cached value?

If cache=false, it's  a different story as per Yonik's
blog.

On Fri, May 6, 2016 at 7:25 AM, Shawn Heisey  wrote:
> On 5/6/2016 12:07 AM, Bastien Latard - MDPI AG wrote:
>> Thank you Susmit, so the answer is:
>> fq queries are by default run before the main query.
>
> Queries in fq parameters are normally executed in parallel with the main
> query, unless they are a postfilter.  I am not sure that the standard
> parser supports being run as a postfilter.  Some parsers (like geofilt)
> do support that.
>
> Susmit already gave you this link where some of that is explained:
>
> http://yonik.com/advanced-filter-caching-in-solr/
>
> Thanks,
> Shawn
>

Re: fq behavior...

[Shawn Heisey]

On 5/6/2016 12:07 AM, Bastien Latard - MDPI AG wrote:
> Thank you Susmit, so the answer is:
> fq queries are by default run before the main query.

Queries in fq parameters are normally executed in parallel with the main
query, unless they are a postfilter.  I am not sure that the standard
parser supports being run as a postfilter.  Some parsers (like geofilt)
do support that.

Susmit already gave you this link where some of that is explained:

http://yonik.com/advanced-filter-caching-in-solr/

Thanks,
Shawn

Re: fq behavior...

[????????]

hello Bastien,


In my memory, fq executed after the usual query!




--  --
??: "Bastien Latard - MDPI AG";<lat...@mdpi.com.INVALID>;
: 2016??5??6??(??) 1:54
??: "solr-user"<solr-user@lucene.apache.org>; 

: fq behavior...



Hi guys,

Just a quick question, that I did not find an easy answer.

 1.

Is the fq "executed" before or after the usual query (q)

e.g.: select?q=title:"something really specific"=bPublic:true=10

Would it first:

  * get all the "specific" results, and then apply the filter
  * OR is it first getting all the docs matching the fq and then
running the "q" query

In other words, does it first check for "the best cardinality"?

Kind regards,
Bastien

Re: fq behavior...

[Bastien Latard - MDPI AG]

Thank you Susmit, so the answer is:
fq queries are by default run before the main query.

kr,
Bast

On 06/05/2016 07:57, Susmit Shukla wrote:

Please take a look at this blog, specifically "Leapfrog Anyone?" section-
http://yonik.com/advanced-filter-caching-in-solr/

Thanks,
Susmit

On Thu, May 5, 2016 at 10:54 PM, Bastien Latard - MDPI AG <
lat...@mdpi.com.invalid> wrote:


Hi guys,

Just a quick question, that I did not find an easy answer.

1.

Is the fq "executed" before or after the usual query (q)

e.g.: select?q=title:"something really specific"=bPublic:true=10

Would it first:

  * get all the "specific" results, and then apply the filter
  * OR is it first getting all the docs matching the fq and then
running the "q" query

In other words, does it first check for "the best cardinality"?

Kind regards,
Bastien




Kind regards,
Bastien Latard
Web engineer
--
MDPI AG
Postfach, CH-4005 Basel, Switzerland
Office: Klybeckstrasse 64, CH-4057
Tel. +41 61 683 77 35
Fax: +41 61 302 89 18
E-mail:
lat...@mdpi.com
http://www.mdpi.com/

Re: fq behavior...

[Susmit Shukla]

Please take a look at this blog, specifically "Leapfrog Anyone?" section-
http://yonik.com/advanced-filter-caching-in-solr/

Thanks,
Susmit

On Thu, May 5, 2016 at 10:54 PM, Bastien Latard - MDPI AG <
lat...@mdpi.com.invalid> wrote:

> Hi guys,
>
> Just a quick question, that I did not find an easy answer.
>
> 1.
>
>Is the fq "executed" before or after the usual query (q)
>
>e.g.: select?q=title:"something really specific"=bPublic:true=10
>
>Would it first:
>
>  * get all the "specific" results, and then apply the filter
>  * OR is it first getting all the docs matching the fq and then
>running the "q" query
>
> In other words, does it first check for "the best cardinality"?
>
> Kind regards,
> Bastien
>
>

fq behavior...

[Bastien Latard - MDPI AG]

Hi guys,

Just a quick question, that I did not find an easy answer.

1.

   Is the fq "executed" before or after the usual query (q)

   e.g.: select?q=title:"something really specific"=bPublic:true=10

   Would it first:

 * get all the "specific" results, and then apply the filter
 * OR is it first getting all the docs matching the fq and then
   running the "q" query

In other words, does it first check for "the best cardinality"?

Kind regards,
Bastien