email thread,
> right?
>
> -- Jack Krupansky
>
> -Original Message- From: Sandeep Gupta
> Sent: Wednesday, October 23, 2013 3:58 AM
> To: solr-user@lucene.apache.org
> Subject: Re: Class name of parsing the fq clause
>
>
> Thanks Jack for detailing out the p
Subject: Re: Class name of parsing the fq clause
Thanks Jack for detailing out the parser logic.
Would it be possible for you to say something more about filter cache code
flow... sometimes we do not use fq parameter in query string and pass the
raw query
Regards
Sandeep
On Mon, Oct 21
Thanks Jack for detailing out the parser logic.
Would it be possible for you to say something more about filter cache code
flow... sometimes we do not use fq parameter in query string and pass the
raw query
Regards
Sandeep
On Mon, Oct 21, 2013 at 7:11 PM, Jack Krupansky wrote:
> Start wit
HI Jack
Thanks a lot for your explanation.
2013/10/21 Jack Krupansky
> Start with org.apache.solr.handler.**component.QueryComponent#**prepare
> which fetches the fq parameters and indirectly invokes the query parser(s):
>
> String[] fqs = req.getParams().getParams(**CommonParams.FQ);
> if (
Start with org.apache.solr.handler.component.QueryComponent#prepare which
fetches the fq parameters and indirectly invokes the query parser(s):
String[] fqs = req.getParams().getParams(CommonParams.FQ);
if (fqs!=null && fqs.length!=0) {
List filters = rb.getFilters();
// if filters already e