[
https://issues.apache.org/jira/browse/SOLR-5542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-5542.
----------------------------
Resolution: Not A Problem
Clarified on mailing list.
Reporter was expecting "defType" to be applied to facet.query...
{quote}
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 alway
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)
{quote}
> Global query parameters to facet queries
> ----------------------------------------
>
> Key: SOLR-5542
> URL: https://issues.apache.org/jira/browse/SOLR-5542
> Project: Solr
> Issue Type: Improvement
> Components: search
> Affects Versions: 4.6
> Reporter: Isaac Hebsh
> Labels: facet
>
> (From the Mailing List)
> 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.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
