Re: Problem with Query Parser

2009-10-18 Thread Lance Norskog
Another way to do multi-lingual indexing is to have a separate field for each language. Solr/Lucene have custom processing for some languages. On Sun, Oct 18, 2009 at 12:25 PM, Germán Biozzoli wrote: > Thanks Ahmet. Definitely using analyzer appears the english porter as > the killer ;) > Regards

Re: Problem with Query Parser

2009-10-18 Thread Germán Biozzoli
Thanks Ahmet. Definitely using analyzer appears the english porter as the killer ;) Regards German On Sun, Oct 18, 2009 at 7:30 AM, AHMET ARSLAN wrote: > >> Hi everybody >> >> I have a simple but (for me) annoying problem. I'm happy >> user of Solr >> 1.4 with a small collection of documents. Tod

Re: Problem with Query Parser

2009-10-18 Thread AHMET ARSLAN
> Hi everybody > > I have a simple but (for me) annoying problem. I'm happy > user of Solr > 1.4 with a small collection of documents. Today one of the > users has > reported that a query returns documents that are > non-pertinent to the > expression. I have spanish, portuguese and english text >

Problem with Query Parser

2009-10-17 Thread Germán Biozzoli
Hi everybody I have a simple but (for me) annoying problem. I'm happy user of Solr 1.4 with a small collection of documents. Today one of the users has reported that a query returns documents that are non-pertinent to the expression. I have spanish, portuguese and english text inside the collectio

Re: Problem with Query Parser?

2009-06-16 Thread Avlesh Singh
Thanks Yonik! Cheers Avlesh On Tue, Jun 16, 2009 at 7:25 PM, Yonik Seeley wrote: > On Tue, Jun 16, 2009 at 8:33 AM, Avlesh Singh wrote: > > Can someone explain this? > > +myField:"\*" +city:Mumbai gives me all results for +city:Mumbai > > > > myField is a regular text field and "*" is not a stop

Re: Problem with Query Parser?

2009-06-16 Thread Yonik Seeley
On Tue, Jun 16, 2009 at 8:33 AM, Avlesh Singh wrote: > Can someone explain this? > +myField:"\*" +city:Mumbai gives me all results for +city:Mumbai > > myField is a regular text field and "*" is not a stopword. * and other non alphanumerics are probably being dropped by WordDelimiterFilter. -Yoni

Re: Problem with Query Parser?

2009-06-16 Thread Avlesh Singh
Can someone explain this? +myField:"\*" +city:Mumbai gives me all results for +city:Mumbai myField is a regular text field and "*" is not a stopword. Cheers Avlesh On Tue, Jun 16, 2009 at 10:26 AM, Yonik Seeley wrote: > On Tue, Jun 16, 2009 at 12:28 AM, Avlesh Singh wrote: > >> > >> Probably th

Re: Problem with Query Parser?

2009-06-15 Thread Yonik Seeley
On Tue, Jun 16, 2009 at 12:28 AM, Avlesh Singh wrote: >> >> Probably the analyzer removed the "$", leaving an empty term and causing >> the clause to be removed altogether. >> > > I predicted this behavior while writing the mail yesterday, Yonik. > Does it sound logical and intuitive? It's intuiti

Re: Problem with Query Parser?

2009-06-15 Thread Avlesh Singh
ring s) { > > > Otis > -- > Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch > > > > - Original Message > > From: Avlesh Singh > > To: solr-user@lucene.apache.org > > Sent: Monday, June 15, 2009 8:06:03 AM > > Subjec

Re: Problem with Query Parser?

2009-06-15 Thread Avlesh Singh
And here's the debug info: +myField:"$" +city:Mumbai +myField:"$" +city:Mumbai +city:Mumbai +city:Mumbai OldLuceneQParser I found this unintuitive. "No results" rather than "All results" was the expected behavior. Cheers Avlesh On Tue, Jun 16, 2009 at 9:58 AM, Avlesh Singh wrote: > Probably th

Re: Problem with Query Parser?

2009-06-15 Thread Avlesh Singh
> > Probably the analyzer removed the "$", leaving an empty term and causing > the clause to be removed altogether. > I predicted this behavior while writing the mail yesterday, Yonik. Does it sound logical and intuitive? Cheers Avlesh On Tue, Jun 16, 2009 at 9:42 AM, Yonik Seeley wrote: > On M

Re: Problem with Query Parser?

2009-06-15 Thread Yonik Seeley
On Mon, Jun 15, 2009 at 11:53 PM, Avlesh Singh wrote: > How does one explain this? > +myField:"$" give zero result > +myField:"$" +city:"Mumbai" gives result for city:"Mumbai" Probably the analyzer removed the "$", leaving an empty term and causing the clause to be removed altogether. -Yonik http

Re: Problem with Query Parser?

2009-06-15 Thread Avlesh Singh
escapeQueryChars(String s) { > > > Otis > -- > Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch > > > > - Original Message > > From: Avlesh Singh > > To: solr-user@lucene.apache.org > > Sent: Monday, June 15, 2009 8:06:03 AM > > Subj

Re: Problem with Query Parser?

2009-06-15 Thread Otis Gospodnetic
(String s) { Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch - Original Message > From: Avlesh Singh > To: solr-user@lucene.apache.org > Sent: Monday, June 15, 2009 8:06:03 AM > Subject: Problem with Query Parser? > > I noticed a strange behavior o

Problem with Query Parser?

2009-06-15 Thread Avlesh Singh
I noticed a strange behavior of the Query parser for the following query on my index. +(category_name:"$" product_name:"$" brand_name:"$") +is_available:1 Fields, category_name, product_name and brand_name are of type "text" and is_available is a "string" field, storing 0 or 1 for each doc in the i