Re: Inconsistent results for facet queries

I'm not sure if that method is viable for reindexing and fetching the whole collection at once for us, but unless there is something inherent in that process which happens at the collection level, we could do it a few shards at a time since it is a multi-tenant setup. I'll see if we can setup a sm

Re: Inconsistent results for facet queries

(1) It doesn't matter whether it "affect only segments being merged". You can't get accurate information if different segments have different expectations. (2) I strongly doubt it. The problem is that the "tainted" segments' meta-data is still read when merging. If the segment consisted of _only_

Re: Inconsistent results for facet queries

We tested the query on all replicas for the given shard, and they all have the same issue. So deleting and adding another replica won't fix the problem since the leader is exhibiting the behavior as well. I believe the second replica was moved (new one added, old one deleted) between nodes and so w

Re: Inconsistent results for facet queries

Never mind. Anything that didn't merge old segments, just threw them away when empty (which was my idea) would possibly require as much disk space as the index currently occupied, so doesn't help your disk-constrained situation. Best, Erick On Thu, Oct 12, 2017 at 8:06 AM, Erick Erickson wrote:

Re: Inconsistent results for facet queries

If it's _only_ on a particular replica, here's what you could do: Just DELETEREPLICA on it, then ADDREPLICA to bring it back. You can define the "node" parameter on ADDREPLICA to get it back on the same node. Then the normal replication process would pull the entire index down from the leader. My

Re: Inconsistent results for facet queries

I thought that decision would come back to bite us somehow. At the time, we didn't have enough space available to do a fresh reindex alongside the old collection, so the only course of action available was to index over the old one, and the vast majority of its use worked as expected. We're planni

Re: Inconsistent results for facet queries

bq: ...but the collection wasn't emptied first This is what I'd suspect is the problem. Here's the issue: Segments aren't merged identically on all replicas. So at some point you had this field indexed without docValues, changed that and re-indexed. But the segment merging could "read" the fir

Inconsistent results for facet queries

Hi, We've run into a strange issue with our deployment of solrcloud 6.3.0. Essentially, a standard facet query on a string field usually comes back empty when it shouldn't. However, every now and again the query actually returns the correct values. This is only affecting a single shard in our setu

Re: Facet queries blow out the filterCache

lect?q=name:boo&rows=1&facet=tru >e >&facet.field=popularity >New values: inserts: lookups: 0, hits: 0, inserts 2, size: 2 > >Same as before... > >http://localhost:8983/solr/techproducts/select?q=name:boo&rows=1&facet=tru >e >&facet.field=popularity

Re: Facet queries blow out the filterCache

e as before... > > http://localhost:8983/solr/techproducts/select?q=name:boo&rows=1&facet=true > &facet.field=popularity > New values: inserts: lookups: 0, hits: 0, inserts 3, size: 2 > > No cache hit! We get an insert instead, but it’s already in there, so the > siz

Re: Facet queries blow out the filterCache

ts 2, size: 2 Same as before... http://localhost:8983/solr/techproducts/select?q=name:boo&rows=1&facet=true &facet.field=popularity New values: inserts: lookups: 0, hits: 0, inserts 3, size: 2 No cache hit! We get an insert instead, but it’s already in there, so the size doesn’t chang

Re: Facet queries blow out the filterCache

: So, no SolrCloud, default example config, about as basic as you get. I : didn’t even bother indexing any docs. Then I issued this query: : : http://localhost:8983/solr/techproducts/select?q=name:foo&rows=1&facet=true : &facet.field=popularity&facet.mincount=0&facet.limit=-1 : This still causes

Re: Facet queries blow out the filterCache

this insert is caused by https://github.com/apache/lucene-solr/blob/trunk/solr/core/src/java/org/apache/solr/search/SolrIndexSearcher.java#L1505 off-top thought: showItems are useless, because now it looks like - item_name:foo:org.apache.solr.search.SortedIntDocSet@​2e1fbd46 Shouldn't it b

Re: Facet queries blow out the filterCache

I backed up a bit. I took the stock solr download and did this: solr-5.3.1>$ bin/solr -e techproducts So, no SolrCloud, default example config, about as basic as you get. I didn’t even bother indexing any docs. Then I issued this query: http://localhost:8983/solr/techproducts/select?q=name:foo&

Re: Facet queries blow out the filterCache

On Thu, 2015-10-01 at 22:31 +, Jeff Wartes wrote: > It still inserts if I address the core directly and use distrib=false. It is quite strange that is is triggered with the direct access. If that can be reproduced in test, it looks like a performance optimization to be done. Anyway, operating

Re: Facet queries blow out the filterCache

logs, btw. It’s definitely facet related though, facet=false eliminates the insert. On 10/1/15, 1:50 PM, "Mikhail Khludnev" wrote: what if you set f.city.facet.limit=-1 ? On Thu, Oct 1, 2015 at 7:43 PM, Jeff Wartes wrote: I’m doing some fairly simple facet queries in a two-s

Re: Facet queries blow out the filterCache

ng by values, it can be seen in logs, btw. > >> >> It’s definitely facet related though, facet=false eliminates the insert. >> >> >> >> On 10/1/15, 1:50 PM, "Mikhail Khludnev" >> wrote: >> >> >what if you set f.city.facet.limit=

Re: Facet queries blow out the filterCache

ail Khludnev" > wrote: > > >what if you set f.city.facet.limit=-1 ? > > > >On Thu, Oct 1, 2015 at 7:43 PM, Jeff Wartes > >wrote: > > > >> > >> I’m doing some fairly simple facet queries in a two-shard 5.3 SolrCloud > >> index on f

Re: Facet queries blow out the filterCache

f you set f.city.facet.limit=-1 ? > >On Thu, Oct 1, 2015 at 7:43 PM, Jeff Wartes >wrote: > >> >> I’m doing some fairly simple facet queries in a two-shard 5.3 SolrCloud >> index on fields like this: >> >> > docValues="true”/> >

Re: Facet queries blow out the filterCache

what if you set f.city.facet.limit=-1 ? On Thu, Oct 1, 2015 at 7:43 PM, Jeff Wartes wrote: > > I’m doing some fairly simple facet queries in a two-shard 5.3 SolrCloud > index on fields like this: > > docValues="true”/> > > that look something like this: > q=

Facet queries blow out the filterCache

I’m doing some fairly simple facet queries in a two-shard 5.3 SolrCloud index on fields like this:

Re: Range Facet queries for date ranges with with non-constant gaps

Thank you. That helped On Tue, Jul 14, 2015 at 5:02 PM, Chris Hostetter wrote: > > : Are there any examples/documentation for IntervalFaceting using dates > that > : I could refer to? > > You just specify the interval set start & end as properly formated date > values. This example shows some

Re: Range Facet queries for date ranges with with non-constant gaps

: Are there any examples/documentation for IntervalFaceting using dates that : I could refer to? You just specify the interval set start & end as properly formated date values. This example shows some range faceting and interval faceting on the same field of the "bin/solr -e techproducts" exam

Re: Range Facet queries for date ranges with with non-constant gaps

Are there any examples/documentation for IntervalFaceting using dates that I could refer to? On Mon, Jul 13, 2015 at 6:36 PM, Chris Hostetter wrote: > > : Some of the buckets return with a count of ‘0’ in the bucket even though > : the facet.range.min is set to ‘1’. That is not the primary issu

Re: Range Facet queries for date ranges with with non-constant gaps

: Some of the buckets return with a count of ‘0’ in the bucket even though : the facet.range.min is set to ‘1’. That is not the primary issue facet.range.min has never been a supported (or documented) param -- you are most likeley trying to use "facet.mincount" (which can be specified per fi

RE: Range Facet queries for date ranges with with non-constant gaps

Try facet.mincount=1. It will still apply to range facets. -Original Message- From: JoeSmith [mailto:fidw...@gmail.com] Sent: Monday, July 13, 2015 5:56 PM To: solr-user Subject: Range Facet queries for date ranges with with non-constant gaps I am trying to do a range facet query

Range Facet queries for date ranges with with non-constant gaps

I am trying to do a range facet query for on date ranges. The query below executes and returns results (almost) as desired for 60DAY buckets. http://localhost:8983/solr/mykeyspace2.user_data/select?wt=json&fq:id=7465033&q=*:*&rows=0&indent=true&facet=on&facet.range=login_event&facet.range.gap=%

Sum as a Projection for Facet Queries

Hi, We have a need of finding the sum of a field for each facet.query. We have looked at StatsComponent but that supports only facet.field. Has anyone written a patch over StatsComponent that supports the same along with some performance measures? Is t

Re: separation of indexes to optimize facet queries without fulltext

t; with different kind of schemas etc? > > Thanks. Daniel > > On Thu, Jul 26, 2012 at 9:05 PM, Chris Hostetter > wrote: > > > > > : My thought was, that I could separate indexes. So for the facet queries > > : where I don't need > > : fulltext sear

Re: separation of indexes to optimize facet queries without fulltext

eplication in SolrCloud e.g with different kind of schemas etc? Thanks. Daniel On Thu, Jul 26, 2012 at 9:05 PM, Chris Hostetter wrote: > > : My thought was, that I could separate indexes. So for the facet queries > : where I don't need > : fulltext search (so also no indexed

Re: separation of indexes to optimize facet queries without fulltext

: My thought was, that I could separate indexes. So for the facet queries : where I don't need : fulltext search (so also no indexed fulltext field) I can use a completely : new setup of a : sharded Solr which doesn't include the indexed fulltext, so the index is : kept small contain

separation of indexes to optimize facet queries without fulltext

Hi, I have currently one big sharded Solr setup storing couple of million documents with some 'small' fields and one fulltext field in each doc. The latter blows up the index. My thought was, that I could separate indexes. So for the facet queries where I don't need fulltext sea

Re: UI support for Multi-Select Facet queries?

e.org > Sent: Friday, December 9, 2011 9:46 AM > Subject: Re: UI support for Multi-Select Facet queries? > > No, multiselect is not wired into /browse. That'd be a nice addition though. > > Erik > > On Dec 8, 2011, at 16:30 , PJ Shimmer wrote: > >> Gree

Re: UI support for Multi-Select Facet queries?

Thanks Erik. Is there any available UI that supports multi-select faceting? From: Erik Hatcher To: solr-user@lucene.apache.org Sent: Friday, December 9, 2011 9:46 AM Subject: Re: UI support for Multi-Select Facet queries? No, multiselect is not wired into

Re: UI support for Multi-Select Facet queries?

No, multiselect is not wired into /browse. That'd be a nice addition though. Erik On Dec 8, 2011, at 16:30 , PJ Shimmer wrote: > Greetings, > > I see that we can query multiple facets for a search with a syntax like > "fq=grade:A OR grade:B". However, I only know how to do this by mo

UI support for Multi-Select Facet queries?

Greetings, I see that we can query multiple facets for a search with a syntax like "fq=grade:A OR grade:B".  However, I only know how to do this by modifying the URL parameter.  Is there a UI component that allows you to select multiple facet values?  I'm thinking something like a checkbox next

Re: naming facet queries?

Yes... use key instead of name in your example below :) On Nov 15, 2011, at 15:12 , Robert Stewart wrote: > Is there any way to give a name to a facet query, so you can pick > facet values from results us

naming facet queries?

Is there any way to give a name to a facet query, so you can pick facet values from results using some name as a key (rather than looking for match via the query itself)? For example, in request handler I have: publish_date:[NOW-7DAY TO NOW] publish_date:[NOW-1MONTH TO NOW] I'd like results to h

Re: Solr 3.4 group.truncate does not work with facet queries

-work-with-facet-queries I'll accept your answer. On Fri, Oct 28, 2011 at 12:14 PM, Martijn v Groningen < martijn.v.gronin...@gmail.com> wrote: > Hi Ian, > > I think this is a bug. After looking into the code the facet.query > feature doesn't take into account the g

Re: Solr 3.4 group.truncate does not work with facet queries

same, as I'd expect - > but unfortunately I'm only interested in the grouped results. > > - I have also asked this question on StackOverflow, here: > http://stackoverflow.com/questions/7905756/solr-3-4-group-truncate-does-not-work-with-facet-queries > > Thanks! > > -- > Ian > > i...@isfluent.com > +44 (0)1223 257903 > -- Met vriendelijke groet, Martijn van Groningen

Solr 3.4 group.truncate does not work with facet queries

only interested in the grouped results. - I have also asked this question on StackOverflow, here: http://stackoverflow.com/questions/7905756/solr-3-4-group-truncate-does-not-work-with-facet-queries Thanks! -- Ian i...@isfluent.com +44 (0)1223 257903

Memory used by facet queries

Hello All. My first time post so be kind. Developing a document store with lots and lots of very small documents. (200 million at the moment. Final size will probably be double this at 400 million documents). This is Proof of concept development so we are seeing what a single code can do for us

Re: "OR" facet queries?

> I want to enable users to select > multiple facet values for a specific facet fields. For > example, if "color" is a facet field, I'd like to let users > to select "red" OR "blue". > > Please note, I've set > > because I want "q=hello+world" means "hello" and "world" > are AND'ed together. > >

"OR" facet queries?

I want to enable users to select multiple facet values for a specific facet fields. For example, if "color" is a facet field, I'd like to let users to select "red" OR "blue". Please note, I've set because I want "q=hello+world" means "hello" and "world" are AND'ed together. 1) What is the synt

Re: How to "OR" facet queries

On Thu, Aug 12, 2010 at 7:12 AM, Frank A wrote: > Hi, I have 3 facet fields (A,B,C) the values of each facet field will > be shown as check boxes to users: > > Field A > [x] Val1a > [x] Val2a > [] Val3a > > Field B > [x] Val1b > [] Val2b > [] Val3b > > Within a field if the user selects two i

How to "OR" facet queries

Hi, I have 3 facet fields (A,B,C) the values of each facet field will be shown as check boxes to users: Field A [x] Val1a [x] Val2a [] Val3a Field B [x] Val1b [] Val2b [] Val3b Within a field if the user selects two items I want the queries to be an "OR" query. Currently I'm generating some

Re: Tagging Facet Queries -- Urgent Help Required

Thanks Erick, On Fri, May 28, 2010 at 2:17 PM, Erik Hatcher wrote: > You've tagged facet queries, but looks like you might want to use the > "excl"ude capability on your filter queries also. Filter queries are > additive, constraining the results further for each one, a

Re: Tagging Facet Queries -- Urgent Help Required

You've tagged facet queries, but looks like you might want to use the "excl"ude capability on your filter queries also. Filter queries are additive, constraining the results further for each one, and by default faceting is based off the search results. Use excl to have

Tagging Facet Queries -- Urgent Help Required

Hi All, I have a use case where I have to tag facet queries. Here is the code snippet for what I tried: query.addFilterQuery("{!tag=NE}med:Blog AND slev:neutral"); query.addFacetQuery("{!tag=NE key=BLOG}med:Blog AND slev:neutral"); query.addFilterQuery("{!tag=P}me

Re: Facet Queries

ki.apache.org/solr/SimpleFacetParameters#Field_Value_Faceting_Parameters > > On Fri, May 14, 2010 at 10:38 AM, Rakhi Khatwani >wrote: > > > Hi, > >whn i use facet queries, whats the default size of the results > > returned? how do we configure if we want all the results shown? > > > > Regards > > Raakhi > > >

Re: Facet Queries

Hey, there´s plenty of documentation about that... http://wiki.apache.org/solr/SimpleFacetParameters#Field_Value_Faceting_Parameters On Fri, May 14, 2010 at 10:38 AM, Rakhi Khatwani wrote: > Hi, >whn i use facet queries, whats the default size of the results > returned?

Facet Queries

Hi, whn i use facet queries, whats the default size of the results returned? how do we configure if we want all the results shown? Regards Raakhi

Re: How does one sort facet queries?

: All sorting of facets works great at the field level (count/index)...all good : there...but how is sorting accomplished with range queries? The solrj : response doesn't seem to maintain the order the queries are sent in, and the The facet_queries section of the facet_counts is in the order that

Re: How does one sort facet queries?

The "trick" I use is to use LocalParams to give eacht facet query a well defined name. Afterwards you can loop through the names in whatever order you want. so basically facet.query={!key=price_0}[* TO 100] etc. N.B. the facet queries in your example will lead to some documents to be counted double (i.e. when the price is exactly 100, 200, 300). Regards, gwk

How does one sort facet queries?

y=price:[500 TO 600] &facet.query=price:[600 TO 700] &facet.query=price:[700 TO *] &facet.mincount=1 &collapse.field=dedupe_hash &collapse.threshold=1 &collapse.type=normal &collapse.facet=before -- View this message in context: http://old.nabble.com/Ho

Re: Default Query Type For Facet Queries

: 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

Re: Default Query Type For Facet Queries

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

Re: Default Query Type For Facet Queries

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

Re: Default Query Type For Facet Queries

stom parser, can I get > : facet-queries to use this custom parser by default as well? > > if you change teh default parser for the entire handler, it should be used > for all query parsing that doesn't use the {!foo} syntax ... but to answer > your orriginal question there is

Re: Default Query Type For Facet Queries

: 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 wel

Re: Default Query Type For Facet Queries

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? -Steph

Re: Default Query Type For Facet Queries

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

Re: Default Query Type For Facet Queries

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

Default Query Type For Facet Queries

We have a custom query parser plugin registered as the default for searches, and we'd like to have the same parser used for facet.query. Is there a way to register it as the default for FacetComponent in solrconfig.xml? I know I can add {!type=customparser} to each query as a workaround, but I'd