Odd ...

This is working fine for us. You have to use the patched Lucene to both
build and do the search and to make sure to use the same analyser. Failing
that, email me the code that you use to build/search the index and I'll have
a look.

HTH,

victor

----- Original Message ----- 
From: "Jianshuo Niu" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, November 25, 2003 7:29 AM
Subject: Re: Dash Confusion in QueryParser - Bug? Feature?


> Dear Victor:
>
> I applied the changed based on the patch. Also, I got t-shirt in the
search query.
> I rebuilt the search index using the modified lucene-1.3-rc2.jar and did
the search by the modified jar as well.
> The search field was specified as indexed, tokenized and stored.
> When I do the search, I did not get any results. I also tried to use the
modified jar to create search query and did the search on the index files
which was built by original lucene-1.3-rc2.jar. It did not get search
results as well. Could you tell me which part I did wrong?
>
> Thanks
>
> Jianshuo
>
> On Mon, 24 Nov 2003 11:15:38 +1100, Victor Hadianto wrote:
>
> > Hi,
> >
> > You missed another change in the file, if you follow that thread I later
> > attached a patch that changes another file (standard tokenizer). Hangon
let
> > me try to find the patch for you.
> >
> >
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgId=764036
> >
> > You also need to change standard tokenizer.
> >
> > Hope this help.
> >
> > /victor
> >
> > ----- Original Message ----- 
> > From: "Jianshuo Niu" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Saturday, November 22, 2003 9:34 AM
> > Subject: Re: Dash Confusion in QueryParser - Bug? Feature?
> >
> >
> >> Dear Victor:
> >>
> >> I read your post on lucene bug list. However, I try the change you
> >> suggested, but it just changed "t-shirts" to "shirt".
> >>
> >> I downloaded lucene1.3-rc1 source, changed the above line in
> >> QueryParser.jj, and recompiled the source. After the change, the query
I
> >> got is:
> >>
> >> +(name:shirt)
> >>
> >> before the change, the query was:
> >>
> >> -(name:shirt)
> >>
> >> I have the following two questions:
> >>
> >> 1. Did I get the results it supposes to be?
> >> 2. in your post, you mentioned only one line change: <#_TERM_CHAR: (
> >> <_TERM_START_CHAR> | <_ESCAPED_CHAR> | "-" ) >
> >> is this only line needs to change?
> >>
> >>
> >>
> >>
> >> Thank you for time and help
> >>
> >>
> >> Jianshuo
> >>
> >>
> >> On Wed, 15 Oct 2003 10:51:28 +1000, Victor Hadianto wrote:
> >>
> >> > Path: main.gmane.org!not-for-mail
> >> > From: "Victor Hadianto" <[EMAIL PROTECTED]>
> >> > Newsgroups: gmane.comp.jakarta.lucene.user
> >> > Subject: Re: Dash Confusion in QueryParser - Bug? Feature?
> >> > Date: Wed, 15 Oct 2003 10:51:28 +1000
> >> > Lines: 14
> >> > Approved: [EMAIL PROTECTED]
> >> > Message-ID: <[EMAIL PROTECTED]>
> >> > References:
<[EMAIL PROTECTED]>
> >> > Reply-To: "Lucene Users List" <[EMAIL PROTECTED]>
> >> > NNTP-Posting-Host: deer.gmane.org
> >> > X-Trace: sea.gmane.org 1066179098 25516 80.91.224.253 (15 Oct 2003
> > 00:51:38
> >> > GMT)
> >> > X-Complaints-To: [EMAIL PROTECTED]
> >> > NNTP-Posting-Date: Wed, 15 Oct 2003 00:51:38 +0000 (UTC)
> >> > Original-X-From:
> >> >
[EMAIL PROTECTED]
> > Wed
> >> > Oct 15 02:51:36 2003
> >> > Return-path:
> >> >
<[EMAIL PROTECTED]>
> >> > Original-Received: from daedalus.apache.org ([208.185.179.12]
> >> > helo=mail.apache.org)
> >> > by deer.gmane.org with smtp (Exim 3.35 #1 (Debian))
> >> > id 1A9Zt1-0004Hs-00
> >> > for <[EMAIL PROTECTED]>; Wed, 15 Oct 2003 02:51:36 +0200
> >> > Original-Received: (qmail 46864 invoked by uid 500); 15 Oct 2003
> > 00:51:23
> >> > -0000
> >> > Mailing-List: contact [EMAIL PROTECTED]; run by
ezmlm
> >> > Precedence: bulk
> >> > List-Unsubscribe: <mailto:[EMAIL PROTECTED]>
> >> > List-Subscribe: <mailto:[EMAIL PROTECTED]>
> >> > List-Help: <mailto:[EMAIL PROTECTED]>
> >> > List-Post: <mailto:[EMAIL PROTECTED]>
> >> > List-Id: "Lucene Users List" <lucene-user.jakarta.apache.org>
> >> > Delivered-To: mailing list [EMAIL PROTECTED]
> >> > Original-Received: (qmail 46822 invoked from network); 15 Oct 2003
> > 00:51:23
> >> > -0000
> >> > Original-Received: from unknown (HELO avalon.siteprotect.com)
> > (64.26.0.99)
> >> > by daedalus.apache.org with SMTP; 15 Oct 2003 00:51:23 -0000
> >> > Original-Received: from victor (CPE-203-51-7-52.nsw.bigpond.net.au
> >> > [203.51.7.52])
> >> > by avalon.siteprotect.com (8.11.6/8.11.6) with ESMTP id h9F0pUU10058
> >> > for <[EMAIL PROTECTED]>; Tue, 14 Oct 2003 19:51:30 -0500
> >> > Original-To: "Lucene Users List" <[EMAIL PROTECTED]>
> >> > X-Priority: 3
> >> > X-MSMail-Priority: Normal
> >> > X-Mailer: Microsoft Outlook Express 6.00.2800.1158
> >> > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
> >> > X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
> >> > Xref: main.gmane.org gmane.comp.jakarta.lucene.user:4555
> >> > X-Report-Spam:
http://spam.gmane.org/gmane.comp.jakarta.lucene.user:4555
> >> > MIME-Version: 1.0
> >> > Content-Type: text/plain; charset=iso-8859-1
> >> > Content-Transfer-Encoding: 7bit
> >> >
> >> >
> >> >> On Tuesday, October 14, 2003, at 08:38  PM, Victor Hadianto wrote:
> >> >> > I believe this is the same problem that I had the other day. If
you
> >> >> > search
> >> >> > the mailing list for "t-shirt" you should get some threads
discussing
> >> >> > this
> >> >> > problem.
> >> >>
> >> >> Haha!  Better search for "shirt", not "t-shirt" :))
> >> >
> >> > If the QueryParser implemented the solution that I suggested then
> > "t-shirt"
> >> > will get you the correct hits :)
> >> >
> >> >
> >> > /vh
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to