RE: query question

2008-02-19 Thread Steven A Rowe
Hi C.B., Yonik is referring to a Solr class: You should theoretically be able to use this filter with straight Lucene code, as long as it's on the classpath. (I'm guessing Yo

Re: query question

2008-02-19 Thread Yonik Seeley
One way is to use WordDelimiterFilter in the analyzer. The example schema has it in the fieldType "text"... also check out http://localhost:8983/solr/admin/analysis.jsp -Yonik On Feb 19, 2008 7:21 AM, Cam Bazz <[EMAIL PROTECTED]> wrote: > Hello, > > I have a tokenized field where I store some inf

Re: query question

2007-08-19 Thread Erick Erickson
Mohammad: See below On 8/19/07, Mohammad Norouzi <[EMAIL PROTECTED]> wrote: > > Erick, > I am using WhitespaceAnalyzer, and yes it's mixed case, in my application > I > never change the entered information to lowercase because of some reasons, I've found it waay easier to index things t

Re: query question

2007-08-18 Thread Mohammad Norouzi
Erick, I am using WhitespaceAnalyzer, and yes it's mixed case, in my application I never change the entered information to lowercase because of some reasons, the thing that I didn't consider was the punctuation in the indexes, but in query I didn't use any punctuation. now using Luke, when I put

Re: query question

2007-08-18 Thread Erick Erickson
I think you'll get much farther much faster if you concentrate on a very simple test case for searching until you get the results you expect. It's particularly telling that you can't get your results from Luke. All the rest of your code is irrelevant until you get what you expect from Luke with a

Re: query question

2007-08-17 Thread Mohammad Norouzi
testn, here is my code but the thing is strange is that by Luke I can't reach my goal as well, look, I have a field (Indexed, Tokenized and Stored) this field has a wide variety of values from numbers to characters, I give the query patientResult:oxalate but the result is no document (using White

Re: query question

2007-08-16 Thread testn
Can you post your code? Make sure that when you use wildcard in your custom query parser, it will generate either WildcardQuery or PrefixQuery correctly. is_maximum wrote: > > Yes karl, when I explore the index by Luke I can see the terms > for example I have a field namely, patientResult, it

Re: query question

2007-08-16 Thread Mohammad Norouzi
Yes karl, when I explore the index by Luke I can see the terms for example I have a field namely, patientResult, it contains value "Ca. Oxalate:many" and also other values such as "Ca. Oxalate:few" etc. the problems are when I put this query: patientResult:(Ca. Oxalate:few) the result is 84329 Ca.

Re: query question

2007-08-15 Thread karl wettin
15 aug 2007 kl. 07.18 skrev Mohammad Norouzi: I am using WhitespaceAnalyzer and the query is " icdCode:H* " but there is no result however I know that there are many documents with this field value such as H20, H20.5 etc. this field is tokenized and indexed what is wrong with this? wh

Re: Query question

2006-11-05 Thread jeff . richley
Chris, thank you so much for your help. I guess I was interpretting the score incorrectly. Wasn't getting it through this thick head, I'm rolling along now. You all have done a great job with this! > > : I know I am getting very close on this one but can't seem to get the > score > : above .306

Re: Query question

2006-11-05 Thread Chris Hostetter
: I know I am getting very close on this one but can't seem to get the score : above .306. My guess is that I need to do something different in my 1) you didn't setOmitNorms(true) 2) why do you care what the score is? .. you said you only wanted exact matches: if you don't tokenize, and you bui

Re: Query question

2006-11-04 Thread jeff . richley
Thought I attached the code :) package com.infinity.naxx.sandbox; import java.io.IOException; import java.util.Iterator; import org.apache.lucene.analysis.Analyzer; import org.apache.lucene.analysis.KeywordAnalyzer; import org.apache.lucene.document.Document; import org.apache.lucene.document.Fi

Re: Query question

2006-11-04 Thread jeff . richley
I know I am getting very close on this one but can't seem to get the score above .306. My guess is that I need to do something different in my query. If at all possible, could you take a quick look at my test code and point me in the correct direction? I know everyone is very busy, so any help w

Re: Query question

2006-11-02 Thread Chris Hostetter
: 1.) I have data like name="Jeff" lastname="Richley" age="33" and I need to : be able to query by any combination such as name="Jeff" age="33". But if : I query with name="Jeffrey" there is no match. : : 2.) The name value pairs are not really controlled until the end user is : inserting informa

Re: Query question

2006-11-02 Thread jeff . richley
Ah good question. The data that I am needing to query on is not a set definition of tables or columns like a database is. Let me give two examples: 1.) I have data like name="Jeff" lastname="Richley" age="33" and I need to be able to query by any combination such as name="Jeff" age="33". But if

Re: Query question

2006-11-02 Thread Erick Erickson
An example (simplified, to be sure) would help a lot. What does a 100% match mean? Why do you care? What problem are you trying to solve? Why wouldn't a database server you better? Best Erick On 11/2/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: I am wanting to be able to put sets of data i

Re: Query question

2006-03-23 Thread Chris Hostetter
: Use "Keyword" (untokenized) field to index your paths. : Consider using PerFieldAnalyzerWrapper to specify KeywordAnalyzer for your path field. : Use the force, Luke - http://www.getopt.org/luke/ , to ensure your paths are indexed correctly. you also don't wnat to use QueryParser.escape when y

Re: Query question

2006-03-22 Thread Otis Gospodnetic
Hi Thomas, Use "Keyword" (untokenized) field to index your paths. Consider using PerFieldAnalyzerWrapper to specify KeywordAnalyzer for your path field. Use the force, Luke - http://www.getopt.org/luke/ , to ensure your paths are indexed correctly. Otis - Original Message From: WATHEL