lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Scott Ganyo <scott.ga...@eTapestry.com>
Subject RE: IndexReader.lastModified() not correct
Date Thu, 08 Aug 2002 16:47:11 GMT
I'd be all for that, but that doesn't work on Winblows either (I just wrote
a test program and checked). 

How about we just have the renameFile() method update the "segments" file
lastModified date and then we won't have to change the lastModified() method
at all...

Scott

> -----Original Message-----
> From: Doug Cutting [mailto:cutting@lucene.com]
> Sent: Thursday, August 08, 2002 11:17 AM
> To: Lucene Developers List
> Subject: Re: IndexReader.lastModified() not correct
> 
> 
> Scott Ganyo wrote:
> > -1.  Now that we've verified that Windows won't work with 
> this proposal
> > without additional checks (and I *really* hate OS-specific 
> checks in Java),
> > I don't think this would be a good idea.
> 
> Here's another approach: have FSDirectory.renameFile() call 
> File.setLastModified() on its directory.  It doesn't need to 
> check what 
> OS is running--this always a correct thing to do.
> 
> Then we can just use the directory's modified time to see 
> when the index 
> has changed, keeping that operation fast and cheap.
> 
> Doug
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:lucene-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: 
> <mailto:lucene-dev-help@jakarta.apache.org>
> 

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message