RE: new Lucene release: 1.2 RC2
Hi, Two weeks back I did have the problem which I stated. But I am unable to reproduce the results currently. I tested and retested but couldnt repeat the same. Doug have U guys fixed the issue long back itself ? (The only thing I have done fresh is to download the latest lucene-1.2-rc1.zip file and re-installed lucene - since it came along with source code) :-) Regards, Sunil Zanjad -Original Message- From: Doug Cutting [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 23, 2001 1:48 AM To: '[EMAIL PROTECTED]'; 'Scott Ganyo'; [EMAIL PROTECTED] Subject: RE: new Lucene release: 1.2 RC2 If you think there is a bug, can you please provide a simple, self-contained, reproducible test case that illustrates the problem. You could use Runtime.getRuntime().halt() to abruptly exit the JVM. Thanks, Doug > -Original Message----- > From: Sunil Zanjad [mailto:[EMAIL PROTECTED]] > Sent: Monday, October 22, 2001 12:49 PM > To: Doug Cutting; 'Scott Ganyo'; [EMAIL PROTECTED] > Subject: RE: new Lucene release: 1.2 RC2 > > > > From: Sunil Zanjad [mailto:[EMAIL PROTECTED]] > > > > >Indexes left in an inconsistent state on crash (i don't > > > remember who > > > > I believe that even I have reported it. This happens on > > abrupt exit of the JVM > > To do this I had one thread updating a directory containing > > many .txt files and > > I simply exited the program. Later when I ran the search, > > it didnt give me the desired output. > > >>That's actually the correct behavior. If indexing is not > completed, with > a > >>call to IndexWriter.close(), then the index should appear unchanged. > > >>Doug > > But what happens to those files which I have indexed > successfully earlier? > The search wouldnt retrieve results of the previous indexed files. > Is this state correct? > Please do clarify on this. > > Regards, > > Sunil Zanjad >
RE: newbi question
Hi,
Except for the import part U have stated everything properly in your source
code.
I tried it out and it works fine.
Hence just check whether the org directory is actually present in the 'D'
drive itself,
and not on some other drive.
I believe that this would surely solve your problem.
Contact me if U wish, I am just a few cubics away...
Regards,
Sunil Zanjad
-Original Message-
From: Parag Dharmadhikari [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 22, 2001 6:36 PM
To: lucene-user
Subject: newbi question
Hi all,
I am new to lucene and I can not understand why I am getting following error
with this program?
public class Search {
public static void main(String[] args) {
try{
String indexPath = "d:\\org", queryString = "parag";
Searcher searcher = new IndexSearcher(indexPath);
Query query = QueryParser.parse(queryString, "body",
new StandardAnalyzer());
Hits hits = searcher.search(query);
for (int i=0; i
RE: new Lucene release: 1.2 RC2
> From: Sunil Zanjad [mailto:[EMAIL PROTECTED]] > > >Indexes left in an inconsistent state on crash (i don't > > remember who > > I believe that even I have reported it. This happens on > abrupt exit of the JVM > To do this I had one thread updating a directory containing > many .txt files and > I simply exited the program. Later when I ran the search, > it didnt give me the desired output. >>That's actually the correct behavior. If indexing is not completed, with a >>call to IndexWriter.close(), then the index should appear unchanged. >>Doug But what happens to those files which I have indexed successfully earlier? The search wouldnt retrieve results of the previous indexed files. Is this state correct? Please do clarify on this. Regards, Sunil Zanjad
RE: new Lucene release: 1.2 RC2
Hi, >Indexes left in an inconsistent state on crash (i don't > remember who I believe that even I have reported it. This happens on abrupt exit of the JVM To do this I had one thread updating a directory containing many .txt files and I simply exited the program. Later when I ran the search, it didnt give me the desired output. I know the type of testing is for extreme rare event in event of power failure or application crash, etc... Is it possible that Lucene would have in future, this kind of rollback ready ? I am surely looking forward to have some feedback on this issue. Regards, Sunil Zanjad -Original Message- From: Scott Ganyo [mailto:[EMAIL PROTECTED]] Sent: Saturday, October 20, 2001 4:05 AM To: 'Doug Cutting'; '[EMAIL PROTECTED]' Subject: RE: new Lucene release: 1.2 RC2 Oops... and the WildcardQuery issues that Robert Lebowitz just reported. > -Original Message- > From: Scott Ganyo [mailto:[EMAIL PROTECTED]] > Sent: Friday, October 19, 2001 5:28 PM > To: 'Doug Cutting'; '[EMAIL PROTECTED]' > Subject: RE: new Lucene release: 1.2 RC2 > > > Well, we know of at least two issues: > > 1) RAMDirectory not merging properly (reported by me) > 2) Indexes left in an inconsistent state on crash (i don't > remember who > reported this) > > Are these to be left as known issues for 1.2? > > Thanks, > Scott > > > -Original Message- > > From: Doug Cutting [mailto:[EMAIL PROTECTED]] > > Sent: Friday, October 19, 2001 4:38 PM > > To: '[EMAIL PROTECTED]' > > Subject: new Lucene release: 1.2 RC2 > > > > > > I just posted a second release candidate for Lucene 1.2. > > This can be found > > at: > > http://jakarta.apache.org/builds/jakarta-lucene/release/v1.2-rc2/ > > > > If no serious bugs are found in the next few days, then I > > will make this the > > 1.2 final release. > > > > Changes from 1.2 RC1: > > - added sources to distribution > > - removed broken build scripts and libraries from distribution > > - SegmentsReader: fixed potential race condition > > - FSDirectory: fixed so that getDirectory(xxx,true) correctly > >erases the directory contents, even when the directory > >has already been accessed in this JVM. > > - RangeQuery: Fix issue where an inclusive range query would > >include the nearest term in the index above a non-existant > >specified upper term. > > - SegmentTermEnum: Fix NullPointerException in clone() method > >when the Term is null. > > - JDK 1.1 compatibility fix: disabled lock files for JDK 1.1, > >since they rely on a feature added in JDK 1.2. > > > > Doug > > >
RE: searche number with lucene
Hi, Try using the org.apache.lucene.analysis.standard.StandardAnalyzer instead of the org.apache.lucene.analysis.StopAnalyzer in IndexFiles.java Also in the SearchFiles.java make use of the same. U would get search on a number Regards, Sunil Zanjad -Original Message- From: eou [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 18, 2001 3:55 AM To: [EMAIL PROTECTED] Subject: searche number with lucene Hello lucene-user, i begin with lucene, and i would like make a search with number ( a year for example). How can i do that? I obtain no result with the demo files. Thanks -- Best regards, eou mailto:[EMAIL PROTECTED]
indexing mechanism failure.....
Hi, The indexing mechanism fails under the following circumstances. This is what I tried out 1. Created indexes on a folder containg .doc files 2. Carried out search on a particular words. Result was obtained accurately. 3. Then I again indexed a particular folder and half way I just aborted the process 4. Carried out the search for the particular words, the end-result was "0 total matching documents" Hence in event of a thread crash or shutting down of the application or simple power failure the indexing does not reflect the existing documents which were indexed previously. This state is highly inconsistent. How do I protect my application from this type of failure? Regards, Sunil Zanjad
