Re: Wildcard question -- case issue

Understood. My solution was to convert any search terms with an asterisk to lowercase prior to submitting to solr and it seems to be working correctly now. Thanks for your help. -- View this message in context: http://old.nabble.com/Wildcard-questioncase-issue-tp27823332p27836740.html Sent f

Wildcard question -- case issue

I'm encountering a potential bug in Solr regarding wildcards. I have two fields defined thusly: and

Issues with spell checker

First of all, I want to thank you guys for your help thus far. It's been very useful during my search-engine integration project. :) So I'm having a few issues with the spell checking component of Solr. For reference, I'm using Solr 1.4. First, I'm not getting any search results period. Here's m

Re: Odd wildcard behavior

Worked exactly as intended. The name field is now indexed as text and the unstemmed "textgen". I have the submission throwing an OR between both for any name searches, and voila. Stemming and wildcard searches are in tact. Thanks!! :) -- View this message in context: http://old.nabble.com/Odd-w

Re: Odd wildcard behavior

It helps tremendously, Erick, and it was the exact idea I had last night after reflecting with a nice scotch. :) I'm planning on indexing the name field as "text" as I have been, and then indexing it again as "nameLiteral" or something with a field type not containing stemming. The code submittin

Re: Odd wildcard behavior

0.0 − 0.0 − 0.0 − 0.0 − 0.0 − 0.0 − 0.0 − 0.0 − 0.0 − 0.0 − 0.0 − 0.0 − 0.0 − 0.0 − 0.0 cjkadakia wrote: > > I'm getting very odd behavior from a wildcard search. > > For example, when I'm searching for docs with a name containing the word > &qu

Odd wildcard behavior

I'm getting very odd behavior from a wildcard search. For example, when I'm searching for docs with a name containing the word "International" the following occur: q=name:(inte*) -- found "International" q=name:(intern*) -- found "International" q=name:(interna*) -- did not find "International"

Re: Range Searches in Collections

about having multiple fee fields, each with just one fee value? > > Otis > > Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch > Hadoop ecosystem search :: http://search-hadoop.com/ > > > > > > From: cjkadaki

Range Searches in Collections

Hi, I'm trying to do a search on a range of floats that are part of my solr schema. Basically we have a collection of "fees" that are associated with each document in our index. The query I tried was: q=fees:[3 TO 10] This should return me documents with Fee values between 3 and 10 inclusively,

Storing values in addition to "last_index_time"

I understand that upon performing an index (full-import or delta-import), the dataimport.properties file is written to with a last_index_time which can then be accessed by the data-config.xml for delta-import queries with ${dataimporter.last_index_time}. I was curious if another key could be adde