Re: searchable mailing list archive

Very nice! Can I know how did you retrieve and store the mails? -- Chris Lu - Full-Text Search on Any Database http://www.dbsight.net On 7/26/05, Alex Krohn <[EMAIL PROTECTED]> wrote: > Hi, > > I've added the Lucene mailing lists to our searchable archive found > here: >

searchable mailing list archive

Hi, I've added the Lucene mailing lists to our searchable archive found here: http://www.gossamer-threads.com/lists/lucene/ The search is, of course, powered by Lucene. =) I hope you find it useful, and thanks for the great work! If you have any questions or problems with it, please feel

RE: Analyzer or QueryParser problem?

your are right its QueryParser throw the exception. I think I got the point. QueryParser doesn't allows asterisk at the begining but SerchIndexer (could) work. For a example when I quering "\**TI" it returned me machings "J400-C-V-S10-T1" and "J400-C-V-S8-T1". -Original Message- From

Re: Analyzer or QueryParser problem?

On Jul 26, 2005, at 7:29 PM, Indu Abeyaratna wrote: I have a question related to this. when I search for wildcard "*11" IndexSearcher throws an exception but when I tries "\**11" it works. I'm guessing QueryParser actually throws an exception, not IndexSearcher, correct? Wildcards at t

RE: Analyzer or QueryParser problem?

I have a question related to this. when I search for wildcard "*11" IndexSearcher throws an exception but when I tries "\**11" it works. I couldn't find any documentation related to this. What could be the reason for this? I am using QueryParser and StandardAnalyser And the query it generate lo

RE: Analyzer or QueryParser problem?

D'OH! That was it! -Original Message- From: Zhang, Lisheng [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 26, 2005 10:25 AM To: java-user@lucene.apache.org Subject: RE: Analyzer or QueryParser problem? Hi Derek, My guessing is that ":" is special, QueryParser may regard ":" as for quali

Querying the values of a field

Hi, I have an index with about 20 different fields. I'd like to query my index to get the list of all different terms for a given field. Is it something possible in a simple way? I mean simpler than getting every terms of the index and then keeping only those which match the given field. Thanks i

RE: Analyzer or QueryParser problem?

Hi Derek, My guessing is that ":" is special, QueryParser may regard ":" as for qualifying a field, we may need to escape this special symbol as: "GM\:Systems" as query string. Regards, Lisheng -Original Message- From: Otis Gospodnetic [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 26,

Re: Analyzer or QueryParser problem?

You can use Luke to see what got indexed. This will tell you what the Analyzer did. You can then use QueryParser from the command line (it's got a main method), give it your input, and see what it returns. This will tell you what QueryParser+Analyzer did. Oh, you use MFQP. It may have a main me

Analyzer or QueryParser problem?

I am working on a business directory app. As you would expect, some companies have unusual names. My first problem is the company with title: "GM:Systems" I indexed the title field as a text field with the English standardAnalyzer. Searching on "GM Systems" will turn it up, but searching on "GM:

Re: filtering on searching or after through hits?

On Jul 26, 2005, at 3:15 AM, Paul Libbrecht wrote: But filters are in-memory biests so have to be recomputed every- time... what would be the best approach: - store the filter (that shouldn't be very expensive but I never tried) - modify the index to add a flag ? Say, for now, my filter cont

Re: filtering on searching or after through hits?

But filters are in-memory biests so have to be recomputed every-time... what would be the best approach: - store the filter (that shouldn't be very expensive but I never tried) - modify the index to add a flag ? Say, for now, my filter contains 70% of the documents. thanks paul Le 25 juil. 05