: You are right, SimpleFacets#getFacetQueryCounts has the following comment:
:
: /* Ignore SolrParams.DF - could have init param facet.query assuming
: * the schema default with query param DF intented to only affect Q.
: * If user doesn't want schema default for facet.query, they shoul
There are also filter queries. Also, in the future we will also add
other query types for other features. Do we want them all to change?
Whatever we do, it should be consistent across all of the query types.
On Fri, Sep 11, 2009 at 9:33 PM, Shalin Shekhar Mangar
wrote:
> On Sat, Sep 12, 2009 at 1
On Sat, Sep 12, 2009 at 12:18 AM, Stephen Duncan Jr <
stephen.dun...@gmail.com> wrote:
> >
> My experience (which is on a trunk build from a few weeks back of Solr
> 2.4),
> is that changing the default parser for the handler does NOT change it for
> facet.query. I had expected it would, but was
On Fri, Sep 11, 2009 at 2:36 PM, Chris Hostetter
wrote:
>
> : I haven't experienced any such problems; it's just a query-parser plugin
> : that adds some behavior on top of the normal query parsing. In any case,
> : even if I use a custom request handler with my custom parser, can I get
> : facet
: I haven't experienced any such problems; it's just a query-parser plugin
: that adds some behavior on top of the normal query parsing. In any case,
: even if I use a custom request handler with my custom parser, can I get
: facet-queries to use this custom parser by default as well?
if you cha
I haven't experienced any such problems; it's just a query-parser plugin
that adds some behavior on top of the normal query parsing. In any case,
even if I use a custom request handler with my custom parser, can I get
facet-queries to use this custom parser by default as well?
-Stephen
On Thu, S
Changing basic defaults like this makes it very confusing to work with
successive solr releases, to read the wiki, etc.
You can make custom search requesthandlers - an example:
customparser
http://localhost:8983/solr/custom?q=string_in_my_custom_language
On 9/10/09, Stephen Dunca
If using {!type=customparser} is the only way now, should I file an issue to
make the default configurable?
--
Stephen Duncan Jr
www.stephenduncanjr.com
On Thu, Sep 3, 2009 at 11:23 AM, Stephen Duncan Jr wrote:
> We have a custom query parser plugin registered as the default for
> searches, an
