Re: Customized Analyzer

2006-12-06 Thread Grant Ingersoll
hit... -Original Message- From: Grant Ingersoll [mailto:[EMAIL PROTECTED] Sent: quarta-feira, 6 de dezembro de 2006 11:33 To: java-user@lucene.apache.org Subject: Re: Customized Analyzer I often find that using Luke (google "luke lucene") gives me the info I need to figure out why I

Re: Customized Analyzer

2006-12-06 Thread Erick Erickson
size() + " products found:"); for(ProductDTO product : products) { System.out.println(product.getName() + " " + product.getModel()); } } -Original Message- From: Chris Hostetter [mailto:[EMAIL PROTECTED] Sent: terça-feira, 5 de dezembro de 2006 20:54 To

RE: Customized Analyzer

2006-12-06 Thread Alice
oleanQuery: contents:wind contents:window and no hit... -Original Message- From: Grant Ingersoll [mailto:[EMAIL PROTECTED] Sent: quarta-feira, 6 de dezembro de 2006 11:33 To: java-user@lucene.apache.org Subject: Re: Customized Analyzer I often find that using Luke (google "luke lucen

Re: Customized Analyzer

2006-12-06 Thread Grant Ingersoll
But still no hits... Any clue? -Original Message- From: Chris Hostetter [mailto:[EMAIL PROTECTED] Sent: terça-feira, 5 de dezembro de 2006 20:54 To: Lucene Users Subject: RE: Customized Analyzer As stated before, a *self contained* test case would help people diagnose your problem ...

RE: Customized Analyzer

2006-12-06 Thread Alice
oleanQuery as I expected: contents:wind contents:window But still no hits... Any clue? -Original Message- From: Chris Hostetter [mailto:[EMAIL PROTECTED] Sent: terça-feira, 5 de dezembro de 2006 20:54 To: Lucene Users Subject: RE: Customized Analyzer As stated before, a *self contained* test

RE: Customized Analyzer

2006-12-06 Thread Alice
.getName() + " " + product.getModel()); } } -Original Message- From: Chris Hostetter [mailto:[EMAIL PROTECTED] Sent: terça-feira, 5 de dezembro de 2006 20:54 To: Lucene Users Subject: RE: Customized Analyzer As stated before, a *self contained* test case would help people diagnos

RE: Customized Analyzer

2006-12-05 Thread Chris Hostetter
As stated before, a *self contained* test case would help people diagnose your problem ... just cutting and pasting a few snippets of your code is not enough for people to reproduce your problem. : And the return is: contents:"(wind window)" a MultiPhraseQuery that looks like that should be fun

Re: Customized Analyzer

2006-12-05 Thread Mark Miller
7;window' was to have a query that would do: Contents:wind contents:window -Original Message- From: Mark Miller [mailto:[EMAIL PROTECTED] Sent: terça-feira, 5 de dezembro de 2006 19:08 To: java-user@lucene.apache.org Subject: Re: Customized Analyzer Just took a quick peak at the MultiPhr

RE: Customized Analyzer

2006-12-05 Thread Alice
would do: Contents:wind contents:window -Original Message- From: Mark Miller [mailto:[EMAIL PROTECTED] Sent: terça-feira, 5 de dezembro de 2006 19:08 To: java-user@lucene.apache.org Subject: Re: Customized Analyzer Just took a quick peak at the MultiPhraseQuery toString() and it does i

RE: Customized Analyzer

2006-12-05 Thread Alice
a-feira, 5 de dezembro de 2006 18:58 To: java-user@lucene.apache.org Subject: Re: Customized Analyzer On Tuesday 05 December 2006 21:37, Alice wrote: > It does not work. > > Even with the synonyms indexed it is not found. So if your text contains "wind" it is not found by the q

Re: Customized Analyzer

2006-12-05 Thread Mark Miller
rça-feira, 5 de dezembro de 2006 18:34 To: java-user@lucene.apache.org Subject: Re: Customized Analyzer On Tuesday 05 December 2006 20:14, Alice wrote: It returns content:"(wind window)" That might be the correct representation of a MultiPhraseQuery. So does your query work a

RE: Customized Analyzer

2006-12-05 Thread Alice
org Subject: Re: Customized Analyzer On Tuesday 05 December 2006 20:14, Alice wrote: > It returns > content:"(wind window)" That might be the correct representation of a MultiPhraseQuery. So does your query work anyway? It's just that you cannot use QueryParser again to pars

Re: Customized Analyzer

2006-12-05 Thread Daniel Naber
On Tuesday 05 December 2006 20:14, Alice wrote: > It returns > content:"(wind window)" That might be the correct representation of a MultiPhraseQuery. So does your query work anyway? It's just that you cannot use QueryParser again to parse this output (similar to some other queries like SpanQue

Re: Customized Analyzer

2006-12-05 Thread Daniel Naber
On Tuesday 05 December 2006 21:37, Alice wrote: > It does not work. > > Even with the synonyms indexed it is not found. So if your text contains "wind" it is not found by the query that prints as content:"(wind window)"? Then I suggest you post a small test case that shows this problem. As Chri

RE: Customized Analyzer

2006-12-05 Thread Alice
o:[EMAIL PROTECTED] Sent: terça-feira, 5 de dezembro de 2006 17:09 To: java-user@lucene.apache.org Subject: Re: Customized Analyzer : I search my synonyms set and if I find something I return the token like: : return new Token(synonyms[i], token.startOffset(), token.endOffset(), : token.type());

Re: Customized Analyzer

2006-12-05 Thread Chris Hostetter
: I search my synonyms set and if I find something I return the token like: : return new Token(synonyms[i], token.startOffset(), token.endOffset(), : token.type()); : And when it gets do the query I see: : : content:"wind window" When you add your synonym, it's just going into the stream of tok