Hi,
I am trying to disable filter cache for some filter queries as they contain
unique ids and cause cache evictions. By adding {!cache=false} the fq is no
longer stored in filter cache, however I have similar conditions in
facet.query and using facet.query={!cache=false}(color:red AND id:XXX
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 com
I am experiencing very slow query time when using multiple facet.query on
large result sets (like 5 minutes).
I don't know how to optimize this, since it is not completely clear to me
how the facet.query works.
Currently my facet queries use tokenized text fields and contain wildcards
or eve
I didn't but I should have ;)
Thx!
-Ursprüngliche Nachricht-
Von: Mikhail Khludnev [mailto:mkhlud...@griddynamics.com]
Gesendet: Dienstag, 3. März 2015 14:48
An: solr-user
Betreff: Re: ex(clude) facet.query ?
you mean
&facet.query={!key="from2" ex="till2"}
you mean
&facet.query={!key="from2" ex="till2"}facet15__d_i:[2.0 TO *]
don;t you?
On Tue, Mar 3, 2015 at 12:00 PM, Clemens Wyss DEV
wrote:
> [Solr 5.0]
> Whereas in
>
> fq={!tag="facet15"}facet15__d_i:1.8 facet15__d_i:2.2
> &q=(*:*)
&
[Solr 5.0]
Whereas in
fq={!tag="facet15"}facet15__d_i:1.8 facet15__d_i:2.2
&q=(*:*)
&facet=true
&facet.mincount=1
&facet.field={!key="facet15" ex="facet15"}facet15__d_i
"facet15" is not affected by the fq (as desired). This does not hold
Whew! Thanks for closing this off.
Best,
Erick
On Fri, Nov 21, 2014 at 9:11 AM, nbosecker wrote:
> Good call - we are adding some ACL to the query going in, and using a Map to
> store the original query values, if there are multiple of the same key, it's
> only storing the last value.
>
> My bad
Good call - we are adding some ACL to the query going in, and using a Map to
store the original query values, if there are multiple of the same key, it's
only storing the last value.
My bad! Thanks for the hint, I wasn't even considering that issue.
Best,
Nancy
--
View this message in context
This is totally weird. What version of Solr? Because the strangest thing
is that the facet.query clause is getting lost on the way _in_. When I tried
this query (5x, I'll admit), at least the echo params at the top had both
facet queries, even when the lastsaveddate was undefined!
In fact
Hi,
I'm having problems with queries that have multiple facet.query fields.
Per the docs:
[http://wiki.apache.org/solr/SimpleFacetParameters#Facet_Fields_and_Facet_Queries]
http://localhost:8983/solr/select?q=video&rows=0&facet=true&facet.field=inStock&facet.query=price:[
;
> https://issues.apache.org/jira/browse/SOLR-1351
>
> Wouldn't using multiple facet.query achieve the same result? I mean
> something like:
>
> facet.query=lastName:A*&facet.query=lastName:B*&facet.query=lastName:C*
>
>
> Bill
>
>
There have been requests for supporting multiple facet.prefix for the same
facet.field. There is an open JIRA with a patch:
https://issues.apache.org/jira/browse/SOLR-1351
Wouldn't using multiple facet.query achieve the same result? I mean
something like:
facet.query=lastName:A*&fa
OK, "problem" solved...
I my tests I only reloaded the core "master" and queried the core "slave".
So config changes on "slave" where not in place :-\
Sorry guys!
Kai
I agree that's definitely strange, I'll have a look at it.
Tommaso
2013/2/12 Chris Hostetter
>
> : > So it seems that facet.query is using the analyzer of type index.
> : > Is it a bug or is there another analyzer type for the facet query?
>
> That doesn&#x
: > So it seems that facet.query is using the analyzer of type index.
: > Is it a bug or is there another analyzer type for the facet query?
That doesn't really make any sense ...
i don't know much about setting up UIMA (or what/when it logs things) but
facet.query uses t
I'm trying to use facets alongside grouping, however when I ask SOLR to compute
grouped facet counts (group.facet=true, see
http://wiki.apache.org/solr/FieldCollapsing) it no longer honours facet.query
excludes, however without this (group.facet=false) the exclude works again
withou
> So it seems that facet.query is using the analyzer of type index.
> Is it a bug or is there another analyzer type for the facet query?
Nobody?
Should I file a bug?
Kai
-Original Message-
From: Kai Gülzau [mailto:kguel...@novomind.com]
Sent: Tuesday, February 05, 2013 2:31 PM
To
Hi all,
which analyzer is used for the facet.query?
This is my schema.xml:
...
When doing a faceting search like:
http://localhost:8983/solr/slave/select?q=*:*&fq=type:7&rows=0&wt=json&indent=true&facet=true&facet.query=albody_de:Kl
facet queries doesn't seem to
work. It will just return the facet count for the selected interval, as it
would without the tag/ex options;
..&fq={!tag=dt}(price:[5 TO 10])&facet.query={!ex=dt}(price:[5 TO 10])
How can I do this?
Thanks
--
View this message in context:
http://lucene.
Thank you very much Hoss, thats exactly what I was looking for ! :)
On Wed, Sep 26, 2012 at 2:12 PM, Chris Hostetter
wrote:
>
> I think you are missunderstanding the purpose of 'facet.query', it doesn't
> change the base query used when faceting, it gives you a count o
I think you are missunderstanding the purpose of 'facet.query', it doesn't
change the base query used when faceting, it gives you a count of
documents that match an arbitrary query.
what you are looking for is a way to "exclude" the fq used to drill down
on the f
o I do something like
this:
q={!edismax qf='field1 field2'}hello AND +Category:Books
facet.query={!edismax qf='field1 field2'}hello
I dont see the original facets. I only see the facet counts for Books. Am I
missing something ? Any help is much appreciated.
Thanks
Kiran
mpalah...@googlemail.com>
> >> wrote:
> >> > Hi Solr community,
> >> >
> >> > Is it possible to return the lowest, highest and average price of a
> >> search
> >> > result using facets?
> >> > I tried something like: facet.qu
ty,
>> >
>> > Is it possible to return the lowest, highest and average price of a
>> search
>> > result using facets?
>> > I tried something like: facet.query={!max(price,0)}
>> > Is it possible and what is the correct syntax?
>> >
>>
2012 at 8:34 AM, Eric Grobler
> wrote:
> > Hi Solr community,
> >
> > Is it possible to return the lowest, highest and average price of a
> search
> > result using facets?
> > I tried something like: facet.query={!max(price,0)}
> > Is it possible and w
something like: facet.query={!max(price,0)}
> Is it possible and what is the correct syntax?
>
> q=htc android
> facet=true
> facet.query=price:[* TO 10]
> facet.query=price:[11 TO 100]
> facet.query=price:[101 TO *]
> ??? facet.query={!max(price,0)}
>
>
> Thanks & Regards
> Ericz
Hi Solr community,
Is it possible to return the lowest, highest and average price of a search
result using facets?
I tried something like: facet.query={!max(price,0)}
Is it possible and what is the correct syntax?
q=htc android
facet=true
facet.query=price:[* TO 10]
facet.query=price:[11 TO 100
e_id:(33 OR
> 44)&facet=on&facet.field={!ex=sources}source_id&facet.query=source_id:(33
> OR 44)&collapse=on&collapse.field=hash_id
>
> I'd like my facet query to return the number of unique documents (based on
> the hash_id field) that are associated to ei
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={!ex=sources}source_id&facet.query=source_
Hello,
I need to create two date facets displaying counts of a particular fields
values.
With normal facets, this can be done with facet.query, but this parameter is
not available to facet.date .
Is this possbile? I'd really prefer to avoid performing two queries.
Thanks
William
--
View
_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 query like this:
>>
>> select?fl=*&start=0&q=cool&fq=in_stock:true&facet=true&am
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
Hi There,
Is there a way to get facet.query= to ignore the fq= param? We want to
do a query like this:
select?fl=*&start=0&q=cool&fq=in_stock:true&facet=true&facet.query=in_stock:false&qt=dismax
To understand the count of items not in stock, when someone has
filtered ite
: > facet.mincount is a way to tell solr not to bother giving you those 0
: > counts ...
:
: An aside: shouldn't that be the default? All of the people using
: facets that I have seen always have to set facet.mincount=1 (or
: facet.zeros=false)
Hmmm... maybe, but it's a really easy option to tur
: I get your point, but how to know where additional metadata is of value
: if not
: just trying? Currently I start with a generic approach to see what
Man power.
for simple schemas the brute force facet on everything appraoch can scale
well .. but as soon as you start talking about having hunda
: Faceting on manufacturers and categories first and than present the
: corresponding facets might be used under some circumstances, but in my case
: the category structure is quite deep, detailed and complex. So when
: the user enters a query I like to say to him "Look, here are the
: manufactu
On 6/20/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
facet.mincount is a way to tell solr not to bother giving you those 0
counts ...
An aside: shouldn't that be the default? All of the people using
facets that I have seen always have to set facet.mincount=1 (or
facet.zeros=false)
-Yonik
: I realized, that the facets are build out of the whole index, not the
: subset
: returned by the initial query. Therefore I have a large number of empty
: facets which I simply ignore. In my case the QueryTime is somewhat
facet.mincount is a way to tell solr not to bother giving you those 0
cou
On Wed, 2007-06-20 at 12:49 -0700, Chris Hostetter wrote:
> : > I solve this problem by having metadata stored in my index which tells
> : > my custom request handler what fields to facet on for each category ...
> : How do you define this metadata?
>
> this might be a good place to start, note th
Chris Hostetter schrieb:
: to make it clear, i agree that it doesn't make sense faceting on all
: available fields, I only want faceting on those 300 attributes that are
: stored together with the fields for full text searches. A
: product/document has typically only 5-10 attributes.
:
: I like t
: to make it clear, i agree that it doesn't make sense faceting on all
: available fields, I only want faceting on those 300 attributes that are
: stored together with the fields for full text searches. A
: product/document has typically only 5-10 attributes.
:
: I like to decide at index time whic
: > I solve this problem by having metadata stored in my index which tells
: > my custom request handler what fields to facet on for each category ...
: How do you define this metadata?
this might be a good place to start, note that this message is almost two
years old, and predates the opensourc
On Wed, 2007-06-20 at 12:59 +0200, Thomas Traeger wrote:
> Martin Grotzke schrieb:
> > On Tue, 2007-06-19 at 19:16 +0200, Thomas Traeger wrote:
[...]
> >> I think it would be really nice, if I don't have to know which facets
> >> fields are there at query time, instead just import attributes into
Martin Grotzke schrieb:
On Tue, 2007-06-19 at 19:16 +0200, Thomas Traeger wrote:
Hi,
I'm also just at that point where I think I need a wildcard facet.field
parameter (or someone points out another solution for my problem...).
Here is my situation:
I have many products of different types
first: sorry for the bad quoting, I found your message in the archive only...
I have many products of different types with totally different
attributes. There are currently more than 300 attributes
I use dynamic fields to import the attributes into solr without having
to define a specific fi
On Tue, 2007-06-19 at 19:16 +0200, Thomas Traeger wrote:
> Hi,
>
> I'm also just at that point where I think I need a wildcard facet.field
> parameter (or someone points out another solution for my problem...).
> Here is my situation:
>
> I have many products of different types with totally dif
On Tue, 2007-06-19 at 11:09 -0700, Chris Hostetter wrote:
> I solve this problem by having metadata stored in my index which tells
> my custom request handler what fields to facet on for each category ...
How do you define this metadata?
Cheers,
Martin
> but i've also got several thousand catego
: I have many products of different types with totally different
: attributes. There are currently more than 300 attributes
: I use dynamic fields to import the attributes into solr without having
: to define a specific field for each attribute. Now when I make a query I
: would like to get bac
Hi,
I'm also just at that point where I think I need a wildcard facet.field
parameter (or someone points out another solution for my problem...).
Here is my situation:
I have many products of different types with totally different
attributes. There are currently more than 300 attributes
On 6/18/07, James Mead <[EMAIL PROTECTED]> wrote:
Is it possible to request all facet.fields for a given facet.query instead
of having to request specific facet.fields? e.g. is there a wildcard for
facet.fields?
Not currently.
Can you elaborate on the problem you are trying to solve? A
Thanks for a great project.
Is it possible to request all facet.fields for a given facet.query instead
of having to request specific facet.fields? e.g. is there a wildcard for
facet.fields?
--
James.
http://blog.floehopper.org
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):
{
&
From: Ge, Yao (Y.)
Sent: Thursday, April 19, 2007 10:41 PM
To: 'solr-user@lucene.apache.org'
Subject: Facet.query
When mutiple facet queries are specified, are they booleaned as OR or
AND?
-Yao
--
regards
jl
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: F
When mutiple facet queries are specified, are they booleaned as OR or
AND?
-Yao
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
you mean by hard-coding them on a
page though. You could have a configuration that specified the
facet.query parameters that get sent, and that same configuration
would be used in making the facet.query parameters as well as driving
the display (mapping, perhaps).
If you have some tho
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
token matches; but facet.query can be used for numeric ranges,
prefix matches, wildcards, etc...
:
: Peter
:
:
: >From: "Peter McPeterson" <[EMAIL PROTECTED]>
: >Reply-To: solr-user@lucene.apache.org
: >To: solr-user@lucene.apache.org
: >Subject: facet.query question
:
ential do you have with
what Solr provides?
Erik
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 Feb 2007 15:10:34 -0800
Hi all,
I'm working wit
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 qu
Hi all,
I'm working with faceted search but I can't seem to get the 'facet.query'
option. I already read the wiki but still don't understand exactly what it
does. Could someone please explain me:
- What does it do and how to use it
- Why should I use it?
- Why sho
62 matches
Mail list logo
