Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Users List" <lucene-user@jakarta.apache.org>
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: AW: boolean AND search
Content-Transfer-Encoding: quoted-printable
Disposition-Notification-To: "Kalthoff,
 Marcus" <Marcus.Kalthoff@solutionline.com>
Date: Thu, 27 Feb 2003 16:30:02 +0100
Message-ID: 
 <7E5CE6BAA209484CA31F26A3FE0509493B7236@srv-lem-ex01.intern.solutionline.com>
Thread-Topic: boolean AND search
Thread-Index: AcLeak6hOl9PpFpaQUef5LmM2hak8gAAmZ5wAADT3aAAAQ0FIA==
From: "Kalthoff, Marcus" <Marcus.Kalthoff@solutionline.com>
To: "Lucene Users List" <lucene-user@jakarta.apache.org>

Sorry,

lucene is perfect. We had a bug in our search-engine wrapper class.=20
It did a .toLowerCase() to the search string so that AND became and.

Thanks

Marcus


> -----Urspr=FCngliche Nachricht-----
> Von: Eric Isakson [mailto:Eric.Isakson@sas.com]
> Gesendet: Donnerstag, 27. Februar 2003 16:06
> An: Lucene Users List
> Betreff: RE: boolean AND search
>=20
>=20
> Have a look at the source for=20
> org.apache.lucene.queryParser.QueryParser.jj the production=20
> in the grammar for the AND operator is:
>=20
>   <AND:       ("AND" | "&&") >
>=20
> and I didn't see anywhere that the token "AND" was being=20
> treated any different than the token "&&"
>=20
> The query parser does not ignore these.
>=20
> The queries
>=20
> 10060 && 10040
>=20
> and
>=20
> 10060 AND 10040
>=20
> and=20
>=20
> +10060 +10040
>=20
> should be equivalent.
>=20
> Have you tried isolating this in a test case outside of your=20
> web application, that would help you be certain this is or is=20
> not a Lucene problem. It should be pretty simple to test.
>=20
> Eric
>=20
> -----Original Message-----
> From: Kalthoff, Marcus [mailto:Marcus.Kalthoff@solutionline.com]
> Sent: Thursday, February 27, 2003 9:37 AM
> To: Lucene Users List
> Subject: AW: boolean AND search
>=20
>=20
> It is a web app, but I am absolutely sure it is correct.=20
> I just wrote a log.debug() to prove this.=20
> I suppose lucene simply ignores AND and OR, because OR is=20
> default anyway.
> But it does not ignore && .
>=20
>=20
> > -----Urspr=FCngliche Nachricht-----
> > Von: Otis Gospodnetic [mailto:otis_gospodnetic@yahoo.com]
> > Gesendet: Donnerstag, 27. Februar 2003 15:14
> > An: Lucene Users List
> > Betreff: Re: boolean AND search
> >=20
> >=20
> > Are you absolutely sure that those & characters are not getting URL
> > encoded (I assume this is a web app)?
> >=20
> > Otis
> >=20
> > --- "Kalthoff, Marcus" <Marcus.Kalthoff@solutionline.com> wrote:
> > > Hi,
> > >=20
> > > I can understand that you need additional + before the=20
> search-words
> > > to get a "real" AND, but what confuses me is that=20
> > >=20
> > > 10060 && 10040
> > >=20
> > > (which should be the same as AND) does a real boolean AND like
> > >=20
> > > +10060 AND +10040  =20
> > >=20
> > > In the query syntax docu, you read "The symbol && can be used in
> > > place of the word AND.". But it is totally different. How do I
> > > explain that to my users?
> > >=20
> > >=20
> > > Marcus
> > >=20
> > >=20
> > > From: Daniel Calvo <dcalvo@ig.com.br>
> > > Subject: Boolean AND query
> > > Date: Thu, 21 Feb 2002 14:12:16 -0300
> > > Content-Type: text/plain;
> > > 	charset=3D"iso-8859-1"
> > >=20
> > > Hi,
> > >=20
> > > To achieve what you want, you need to use the required operand (+)
> > >=20
> > > --Daniel=20
> > >=20
> > > > -----Original Message-----
> > > > From: Aruna Raghavan [mailto:ArunaR@opin.com]
> > > > Sent: quinta-feira, 21 de fevereiro de 2002 13:44
> > > > To: 'Lucene Users List'
> > > > Subject: Boolean AND query
> > > >=20
> > > >=20
> > > > Hello,
> > > > Has anyone run into problems with boolean AND query?=20
> Basically, I
> > > am using
> > > > the following code to do the query to look for=20
> > > > 10060 AND 10040
> > > >=20
> > > > BooleanQuery bq =3D new BooleanQuery();
> > > > Analyzer analyzer =3D new StandardAnalyzer();
> > > > Query query =3D QueryParser.parse(m_strKeyword, "pageText",
> > > analyzer);
> > > >  bq.add(query, true, false);
> > > >=20
> > > > In this case, I am just using one query to add to bq=20
> but there can
> > > be more.=20
> > > >=20
> > > > I am getting correct results when 10060 AND 10040 exists in the
> > > document.
> > > > But when one of them does not exist, I am still getting the same
> > > results. In
> > > > other words, AND seems to be acting like an OR. I=20
> noticed this in
> > > the latest
> > > > RC4 as well as an older lucene build from before lucene joined
> > > jakarta.
> > >=20
> > >=20
> >=20
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail:=20
> lucene-user-help@jakarta.apache.org
> > >=20
> >=20
> >=20
> > __________________________________________________
> > Do you Yahoo!?
> > Yahoo! Tax Center - forms, calculators, tips, more
> > http://taxes.yahoo.com/
> >=20
> >=20
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: lucene-user-help@jakarta.apache.org
> >=20
> >=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>=20
>=20

---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org