t for about a minute before gathering this data. The spreadsheets are
output from Solr Meter. I can post logs if that's easier to look at.
- Hayden
On Fri, Jul 18, 2014 at 11:48 AM, Yonik Seeley
wrote:
> On Fri, Jul 18, 2014 at 2:10 PM, Hayden Muhl wrote:
> > I was doing some pe
I was doing some performance testing on facet queries and I noticed
something odd. Most queries tended to be under 500 ms, but every so often
the query time jumped to something like 5000 ms.
q=*:*&fq={!tag=productBrandId}productBrandId:(156
1227)&facet.field={!ex=productBrandId}productBrandId&face
gt; personal recommendation is to use this in a separated field that get’s
> populated through a copyField, this way you could apply different boosts.
>
> Greetings,
>
> On Jul 16, 2014, at 2:00 PM, Hayden Muhl wrote:
>
> > A copy field does not address my problem, and th
treat
each token like a prefix?
On Tue, Jul 15, 2014 at 4:55 PM, Alexandre Rafalovitch
wrote:
> So copyField it to another and apply alternative processing there. Use
> eDismax to search both. No need to store the copied field, just index it.
>
> Regards,
> Alex
> On 16/07
tps://www.linkedin.com/groups?gid=6713853
>
>
> On Tue, Jul 15, 2014 at 8:04 AM, Hayden Muhl wrote:
> > I'm working on using Solr for autocompleting usernames. I'm running into
> a
> > problem with the wildcard queries (e.g. username:al*).
> >
> > We are
I'm working on using Solr for autocompleting usernames. I'm running into a
problem with the wildcard queries (e.g. username:al*).
We are tokenizing usernames so that a username like "solr-user" will be
tokenized into "solr" and "user", and will match both "sol" and "use"
prefixes. The problem is w
I'm working on a user name autocomplete feature, and am having some issues
with the way we are tokenizing user names.
We're using the StandardTokenizerFactory to tokenize user names, so
"foo-bar" gets split into two tokens. We take input from the user and use
it as a prefix to search on the user n
olr? There was a library loading bug with multiple
> cores. Not a perfect match to your description but close enough.
>
> Regards,
> Alex
> On 21 Sep 2013 02:28, "Hayden Muhl" wrote:
>
> > I have two cores "favorite" and "user" running in the
I have two cores "favorite" and "user" running in the same Tomcat instance.
In each of these cores I have identical field types "text_en", "text_de",
"text_fr", and "text_ja". These fields use some custom token filters I've
written. Everything was going smoothly when I only had the "favorite" core.
I've been playing around with the PositionLengthAttribute for a few days,
and it doesn't seem to have any effect at all.
I'm aware that position length is not stored in the index, as explained in
this blog post.
http://blog.mikemccandless.com/2012/04/lucenes-tokenstreams-are-actually.html
Howeve
A search for a single character will only return hits if that character
makes up a whole word, and only if the tokenizer recognizes that character
as a word. It's just like in other languages, where a search for "p" won't
return documents with the word "apple".
If I were you, I would go into the S
I've read the documentation about how you can configure a Solr core with a
properties file. Is there any way to specify a properties file that will
apply to all cores running on a server?
Here's my scenario. I have a solr setup where I have two cores, "foo" and
"bar". I want to enable replication
12 matches
Mail list logo
