On Jul 6, 2004, at 1:08 AM, Karthik N S wrote:
Can SomeBody Tell me Where Can I find Latest copy of
StopAnalyzer.java
which can be used with Lucene1_4-final,
On Lucene-Sandbox I am not able to Find it.
[ My Company Prohibits me from using CVS ]
Note that force is really just 'suggest'. Regardless, I have seen apps
running under 1.3.1 JVM where this worked.
Otis
--- David Spencer [EMAIL PROTECTED] wrote:
This in theory should not help, but anyway, just in case, the idea is
to
call gc() periodically to force gc - this is the code I
Hi
Dev Guys
Apologies.
I have 3 Questions for u.
1)
I have a situation in here where I am suppose to group unique indexerd
Documents
depending upon the number of hit's per document.
To Breifly Explain this
All documet with n hits for a Search word would be grouped under
Hi!
I'm using Lucene 1.3 final currently, all things were working fine.
But, after i'm upgraded from Lucene 1.3 final to 1.4rc3 (simply overwrite the
lucene-1.4-final.jar to lucene-1.4-rc3.jar and re-compile it)
We can re-compile it successfuly. but when will try to index the document. It give
Hey
Apologies
Same with me tooo...
The no of Hits on set of Documents indexed using 1.3-final is not same
on 1.4-final version
[ The only modification done to the src is , I have upgraded my
CustomAnalyzer on basis of StopAnalyzer avaliable in 1.4 ]
Does doing this effect the
I'm trying to burn an index of 14M documents.
I have two problems.
1. I have to run optimize() every 50k documents or I run out of file
handles. this takes TIME and of course is linear to the size of the
index so it just gets slower by the time I complete. It starts to crawl
at about 3M
