lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Hostetter <hossman_luc...@fucit.org>
Subject Re: Why IndexReader.lastModified(index) is depricated?
Date Thu, 20 Jan 2005 05:06:26 GMT

: Why IndexReader.lastModified(index) is depricated?

Did you read the javadocs?

   Synchronization of IndexReader and IndexWriter instances is no longer
   done via time stamps of the segments file since the time resolution
   depends on the hardware platform. Instead, a version number is
   maintained within the segments file, which is incremented everytime
   when the index is changed.

: It's always a good idea to know when the index changed last time, for

That's a good point, and you can still get that information using the same
underlying method IndexReader.lastModified did/does...

     directory.fileModified("segments");

...it's just no longer crucial that IndexReader have that information.



-Hoss


---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org


Mime
View raw message