RE: how to get newest library version?

Ok thanks, this works *is building the new jar at the moment* -Oorspronkelijk bericht- Van: Paul Elschot [mailto:[EMAIL PROTECTED] Verzonden: woensdag 24 augustus 2005 8:30 Aan: java-user@lucene.apache.org Onderwerp: Re: how to get newest library version? On Tuesday 23 August 2005

Search Results Clustering

Hi All, I have been using Lucene in my application to search over 4 million recordes updated daily. I am currently using a single index with 21 fields. Some of my fields contain numbers that are foreign keys to my data. I have provided a dropdown of values to select from, on my search form, to

RE: QueryParser not thread-safe

Thanks for pointing that out! I checked the source and QueryParser is indeed not thread-safe (the presence of local variables like jj_lastpos that are used *during* the parsing makes this obvious) Perhaps it should be explicitly mentioned in the javadoc. The solution I'll probably go for is

Re: QueryParser not thread-safe

I would just create a new QueryParser for each query. Allocating short-lived objects is just about free in java, and the time spent performing the actual search will by far dominate any time spent constructing QueryParser objects. On 8/24/05, Vanlerberghe, Luc [EMAIL PROTECTED] wrote: Thanks

Re: Search Results Clustering

well you're not going to like my answer, to that, if what you're looking for is a group by result depending on the unique values of a field or a combination of fields ( field-3 field-4 ), something that in SQL would look like this : select field-3 , field-4 , count(*) from ... where .

Re: UpdateIndex

Hi, what can i do with files which are deleted from the document directory? How can i delete them from the index, if i start an update? Currently i start a search in the index for existing documents and delete them, when they have changed! After that session i add all the documents, which are

OutOfMemory when calling SegmentTermEnum.growBuffer(..) during search

We have a Lucene powered search with approx 1,2 million documents indexed. We get sporadic OutOfMemory errors when users search this index (have tried rebuilding the index several times from scratch), as Lucene tries to allocate over 500 MB of memory. Luke reports the following details: Number of

Re: OutOfMemory when calling SegmentTermEnum.growBuffer(..) during search

On Wednesday 24 August 2005 13:07, Fredrik wrote: bsh % i = d.openFile(copy.tii); bsh % print (i.readVInt()); 266338303 I haven't looked in the source, but according to the documentation the first value is supposed to be a version number: http://lucene.apache.org/java/docs/fileformats.html

Re: QueryParser not thread-safe

Thanks for all the answers! Now, while I agree that simple is better, I think QueryParser should be made thread-safe through the use of a wrapper class (along the line of what Luc suggested) or by using something other than javacc, so this is no longer an issue in future lucene versions. I

Re: QueryParser not thread-safe

On Wed, 2005-08-24 at 12:10 -0300, [EMAIL PROTECTED] wrote: Now, while I agree that simple is better, I think QueryParser should be made thread-safe through the use of a wrapper class (along the line of what Luc suggested) or by using something other than javacc, so this is no longer an

Re: UpdateIndex

Would you want to update, or could you just append to an existing Index? Thanks, B --- Ray Tsang [EMAIL PROTECTED] wrote: This could be off topic, but I made something that updates indices that worked like the following, wonder if anybody has the same ideas? I found something like

Re: Search Results Clustering

the approach(es) I described in this thread... http://mail-archives.apache.org/mod_mbox/lucene-java-user/200505.mbox/[EMAIL PROTECTED] ...should work, but you have the added complexity of whating the counts not just for all unique values in a field, but all the permutations of values from two

Document visible by Term, but not search

I have the following strange behavior for an index. The index has been optimized and has no deletions. It's in compound file format. Using Luke 0.6 I can browse by Term and find my term (ItemId:727680). It's a Keyword field. It shows a docfreq of this term is 1. It also shows all the document

Re: Document visible by Term, but not search

Dan Climan wrote: I have the following strange behavior for an index. The index has been optimized and has no deletions. It's in compound file format. Using Luke 0.6 I can browse by Term and find my term (ItemId:727680). It's a Keyword field. It shows a docfreq of this term is 1. It also shows

Re: Document visible by Term, but not search

Hi Dan, What's the term? Could this be an analyzer problem? Are you using the same analyzer for indexing and searching? Fred At 09:06 PM 8/24/2005, you wrote: I have the following strange behavior for an index. The index has been optimized and has no deletions. It's in compound file format.

Thinking about better highlighting

All, First, my thanks to those who've contributed to the current best practices for highlighting. We use your code! However, after reviewing recent discussions about highlighting, and struggling with our own highlighting issues, I'm wondering if there's a better way. Others have certainly

RE: Lucene and Xanga.com

Otis, we've been continually impressed with the performance of Lucene. We've been ever increasing the load we are putting on it (from our small help section, to our slightly larger metros, to our big groups, and then our gigantic weblogs), and it has meet each of these challenges wonderfully.

Phrase frequency

How can I get phrase frequency in an index? termDocs/termPositions in IndexReader work only with words Thanks Ravi. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]