Do we really need CJKAnalyzer to search japanese characters

Hello all, You will have to excuse me if the question looks dumb ;) I didn't use CJKAnalyzer and I could still search japanese characters. Actually I used it first but then I thought of testing with just the standard analyzer. It worked with standard analyzer also. I was able to search the meta

Re: To anyone who has used Luke

James Dunn wrote: I've seen that too. I'm pretty sure either Lucene is creating it, or it's an issue with Luke. (I'm the author of Luke) The problem lies with Lucene, unfortunately. The method IndexReader.getFieldNames() returns an additional blank at the end. This is already reported as a bug,

Re: To anyone who has used Luke

I've seen that too. I'm pretty sure either Lucene is creating it, or it's an issue with Luke. Jim --- Don Vaillancourt <[EMAIL PROTECTED]> wrote: > Hello All, > > I'm using Luke, the software that someone mentioned > before. It's great for > debugging. My question to anyone who has used it.

To anyone who has used Luke

Hello All, I'm using Luke, the software that someone mentioned before. It's great for debugging. My question to anyone who has used it. Under the overview tab in the available fields column on the left is listed all the columns that I wanted indexed and/or stored and/or tokenized. I only def

Re: Lucene Error

Hello, Someone replied to me off-list and suggested to me the same thing and it did resolve the problem. Thanks At 12:37 PM 25/06/2004, you wrote: Hello Don, I've never seen this, and I'm pretty sure it's not really Lucene's fault. Lucene is aware only of segments/files listed in segments file.

Optimizing for long queries?

Apologies if this is a FAQ, but I didn't have much luck searching the list archives for answers on this subject: I'm using Lucene in a context where we have frequently have queries that search for as many as 30-50 terms in a single field. Does anyone have any thoughts concerning ways optimize Luce

Re: QueryParser and Keyword Fields

On Jun 25, 2004, at 1:41 PM, [EMAIL PROTECTED] wrote: Can anyone give me advice on the best way to not have your keyword fields analyzed by QueryParser? Even though it seems like it would be a common problem, I have read the FAQ, and found this relevant thread with no real answers. http://iss

ANN: Experimental site for searching javadoc of OSS projects

I've put together a kind of experimental site which indexes the javadoc of OSS java projects (well, plus the JDK). http://www.searchmorph.com/ This is meant to solve the problem where a java developer knows something has been done before, but where, in what project - source forge? jakarta? ecli

QueryParser and Keyword Fields

Can anyone give me advice on the best way to not have your keyword fields analyzed by QueryParser? Even though it seems like it would be a common problem, I have read the FAQ, and found this relevant thread with no real answers. http://issues.apache.org/eyebrowse/[EMAIL PROTECTED] he.org&msgId=12

Re: Lucene Error

Hello Don, I've never seen this, and I'm pretty sure it's not really Lucene's fault. Lucene is aware only of segments/files listed in segments file. Could it have anything to do with that ColdFusion code that wraps Lucene by any chance? Regardless, it's probably not the best practise to store n

Re: best mergeFactor for merging 100 Indexes

If this is an option, use compund index format (writer.setUseCompound(true)). ulimit -a in some UNIX shells will tell you the max number of open files allowed. If you can, increase that number as high as you can. Of course, how high you can go also depends on your RAM. Finally, don't forget the

Re: Index MSOffice Documents

Thanks Sergiu, You should also post to the Lucene Users list. -Ryan - Original Message - From: "Sergiu Gordea" <[EMAIL PROTECTED]> To: "Lucene Users List" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Cc: "POI Users List" <[EMAIL PROTECTED]> Sent: Friday, June 25, 2004 8:42 AM Subject: Index

Lucene Error

Hello All, I'm using Lucene to build collections from ColdFusion which I've got working pretty good so far. But I am getting the following exception for some reason that I can't understand and never used to get before. Below is the stack trace for that error. Lucene is telling me that it cann

best mergeFactor for merging 100 Indexes

Hi, after an hour of indexing on a cluster I got 100 Indexes, ca. 25MB each, 2 indexed fields. I intend now to run code roughly like IndexWriter writer = new IndexWriter(destDir, ...); writer.addIndexes(my100IndexDirs); writer.close() When I did this a year ago, I know I had tough probl

multiple select box parameter passing to jsp page causes error

Hi all, I am developing a html page in which there is a multiple selection box taht indicates the Indexed fields to be searched upon. Also, it has as the default option the All Fields option. Now, some fields (options) are allowed to be selected in combination.This means that the parame

Index MSOffice Documents

Hi all, I'm working on a project in which we are building a knowledge management platform. We are using Turbine/Velocity as framework and we are using lucene for search. We want to make the search to be able to index MSOffice Documents, therefore I was searching for some possibilities to extract

Re: Various kind of queries

> code I posted a while ago: > > http://java2.5341.com/msg/51792.html > > Note: is this the only archive of lucene-user? I thought it used to > be somewhere else... I tend to use EyeBrowse on nagoya.apache.org, but there are at least 2 other sites with full archives of lucene-* and many other li

Re: ANN: Luke v. 0.5 released

On Thu, 24 Jun 2004 12:34:35 +0200 Andrzej Bialecki <[EMAIL PROTECTED]> wrote: Vladimir Yuryev wrote: Hi Andrzej! I am sorry for my English :-( I with pleasure shall tell about the test and I shall try to state conditions of the test in detail. I don't quite understand what you are saying...