ds using an analyzer will break
> > wildcard search. If there is a wildcard, the query analyzer doesn't run
> > filters, so it won't prepend the user id. I could prepend the user id
> > myself before calling Solr, but that seems... bad.
> >
> > Scott
> >
n't prepend the user id. I could prepend the user id
> myself before calling Solr, but that seems... bad.
>
> Scott
>
>
>
> > -Original Message-
> > From: Scott Schneider [mailto:scott_schnei...@symantec.com]
> > Sent: Thursday, November 07, 2013
2013 2:03 PM
> To: solr-user@lucene.apache.org
> Subject: RE: fq efficiency
>
> Thanks, that link is very helpful, especially the section, "Leapfrog,
> anyone?" This actually seems quite slow for my use case. Suppose we
> have 10,000 users and 1,000,000 documents. We
lyograg.org]
> Sent: Tuesday, November 05, 2013 4:35 PM
> To: solr-user@lucene.apache.org
> Subject: Re: fq efficiency
>
> On 11/5/2013 3:36 PM, Scott Schneider wrote:
> > I'm wondering if filter queries are efficient enough for my use
> cases. I have lots and lots of use
On 11/5/2013 3:36 PM, Scott Schneider wrote:
I'm wondering if filter queries are efficient enough for my use cases. I have
lots and lots of users in a big, multi-tenant, sharded index. To run a search,
I can use an fq on the user id and pass in the search terms. Does this scale
well with th
Hi all,
I'm wondering if filter queries are efficient enough for my use cases. I have
lots and lots of users in a big, multi-tenant, sharded index. To run a search,
I can use an fq on the user id and pass in the search terms. Does this scale
well with the # users? I suppose that, since user
