Re: Global query parameters to facet query

2013-12-10 Thread Chris Hostetter

: when disabling the facet, the query works perfectly. I understand that
: either defType parameter or q.myalias.qf parameters, do not affect the
: facet query (which always runs with lucene parser??)

a top level defType param only applies to the q param.  This is by 
design.  

defType is special and only applies to hte main query where it is 
being evaluated, in order to make it easier to specify the type of parser 
to use on input straight from end users -- things like fq, facet.query, 
and any recursively specified query strings (ie: via other nested local 
params), etc, are not affected by defType.  These other params are almost 
always programatically generated, so it's typically easy to use an 
explicit type local param to change the parser they use (if they looked 
at defType it would cause all sorts of confusing behavior for most users 
who just wanted to cahnge the parser for the main query)


-Hoss
http://www.lucidworks.com/


Re: Global query parameters to facet query

2013-12-09 Thread Isaac Hebsh
created SOLR-5542.
Anyone else want it?


On Thu, Dec 5, 2013 at 8:55 PM, Isaac Hebsh isaac.he...@gmail.com wrote:

 Hi,

 It seems that a facet query does not use the global query parameters (for
 example, field aliasing for edismax parser).
 We have an intensive use of facet queries (in some cases, we have a lot of
 facet.query for a single q), and the using of LocalParams for each
 facet.query is not convenient.

 Did I miss a normal way to solve it?
 Did anyone else encountered this requirement?



Re: Global query parameters to facet query

2013-12-09 Thread Chris Hostetter
: It seems that a facet query does not use the global query parameters (for
: example, field aliasing for edismax parser).

can you please give a specific example of a query that isn't working for 
you?

Using this query against the examle data, things work exactly as i would 
expect showing that the QParsers used for facet.queries inherit the 
global params (unless overridden by local params of course)...

http://localhost:8983/solr/select?q=*:*wt=jsonindent=truefacet=truefacet.query={!dismax}solr+bogusfacet.query={!dismax%20mm=1}solr+bogusfacet.query={!dismax%20mm=1%20qf=%27foo_t%27}solr+bogusrows=0mm=2qf=name
{
  responseHeader:{
status:0,
QTime:2,
params:{
  mm:2,
  facet:true,
  indent:true,
  facet.query:[{!dismax}solr bogus,
{!dismax mm=1}solr bogus,
{!dismax mm=1 qf='foo_t'}solr bogus],
  q:*:*,
  qf:name,
  wt:json,
  rows:0}},
  response:{numFound:32,start:0,docs:[]
  },
  facet_counts:{
facet_queries:{
  {!dismax}solr bogus:0,
  {!dismax mm=1}solr bogus:1,
  {!dismax mm=1 qf='foo_t'}solr bogus:0},
facet_fields:{},
facet_dates:{},
facet_ranges:{}}}






-Hoss
http://www.lucidworks.com/


Global query parameters to facet query

2013-12-05 Thread Isaac Hebsh
Hi,

It seems that a facet query does not use the global query parameters (for
example, field aliasing for edismax parser).
We have an intensive use of facet queries (in some cases, we have a lot of
facet.query for a single q), and the using of LocalParams for each
facet.query is not convenient.

Did I miss a normal way to solve it?
Did anyone else encountered this requirement?