facet.query is really just a short-cut for numFound using that query standalone.
How many facet.query’s are you issuing? And what is the QTime for all those
queries when individually made like this:
/select?q=&rows=0
If one of your queries is “slow” - you mention wildcards and complex phra
http://wiki.apache.org/solr/FieldCollapsing#Known_Limitations
> Hi All,
>
> I'm in a situation where I need to perform a facet on a query with field
> collapsing.
>
> Let's say the main query is something like this
>
> title:apple&fq={!tag=sources}source_id:(33 OR
> 44)&facet=on&facet.field={!e
Thanks, that was just what I was looking for!
On Tue, Oct 27, 2009 at 1:27 PM, Jérôme Etévé wrote:
> Hi,
>
> you need to 'tag' your filter and then exclude it from the faceting.
>
> An example here:
> http://wiki.apache.org/solr/SimpleFacetParameters#Tagging_and_excluding_Filters
>
> J.
>
> 200
Hi,
you need to 'tag' your filter and then exclude it from the faceting.
An example here:
http://wiki.apache.org/solr/SimpleFacetParameters#Tagging_and_excluding_Filters
J.
2009/10/27 David Giffin :
> Hi There,
>
> Is there a way to get facet.query= to ignore the fq= param? We want to
> do a
On Apr 19, 2007, at 10:41 PM, Ge, Yao ((Y.)) wrote:
When mutiple facet queries are specified, are they booleaned as OR or
AND?
Neither, if you're referring to &facet.query=...
facet.query's are all appended to the response, like this (in Ruby
response format):
{
'responseHeader'=>{
'sta
I think it only concern with QueryWord, not about Facet。
2007/4/20, Ge, Yao (Y.) <[EMAIL PROTECTED]>:
Never mind. I should have read the example
(http://wiki.apache.org/solr/SimpleFacetParameters#head-1da3ab3995bc4abc
dce8e0f04be7355ba19e9b2c) first.
From: Ge
Never mind. I should have read the example
(http://wiki.apache.org/solr/SimpleFacetParameters#head-1da3ab3995bc4abc
dce8e0f04be7355ba19e9b2c) first.
From: Ge, Yao (Y.)
Sent: Thursday, April 19, 2007 10:41 PM
To: 'solr-user@lucene.apache.org'
Subject: Facet.query
I meant facet.query, not fq, in the example below. fq is a filter
query, whereas filter.query is a, umm, filter.query.
Erik
On Feb 1, 2007, at 9:19 PM, Erik Hatcher wrote:
On Feb 1, 2007, at 7:55 PM, Peter McPeterson wrote:
Well, I think I figured it out. It can be used to display
ughts on Solr providing more assistance here,
please share.
I envision Flare providing a lot of this sort of UI goodness.
Erik
Thanks.
Peter
From: Erik Hatcher <[EMAIL PROTECTED]>
Reply-To: solr-user@lucene.apache.org
To: solr-user@lucene.apache.org
Subject: Re: facet.query questi
them into an
array and doing like "1980 - 1989 ("+array[0]+")", "1980 - 1989
("+array[1]+")" and so forth) and I don't think its the best way.
Thanks.
Peter
From: Erik Hatcher <[EMAIL PROTECTED]>
Reply-To: solr-user@lucene.apache.org
To: solr
: Well, I think I figured it out. It can be used to display count results of
: different facet queries.
:
: But is it all that it does?
pretty much ... it's provided as a simple way to get the facet constraint
count for an arbitrary query (or queries) .. facet.field is usefull for
simpel token ma
On Feb 1, 2007, at 7:55 PM, Peter McPeterson wrote:
Well, I think I figured it out. It can be used to display count
results of different facet queries.
But is it all that it does?
Yes. This allows for dynamic "facets" based on run-time queries
rather than an upfront indexed (and often un
Well, I think I figured it out. It can be used to display count results of
different facet queries.
But is it all that it does?
Peter
From: "Peter McPeterson" <[EMAIL PROTECTED]>
Reply-To: solr-user@lucene.apache.org
To: solr-user@lucene.apache.org
Subject: facet.query question
Date: Thu, 01
13 matches
Mail list logo