lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Gaunt" <SGa...@emeraldinsight.com>
Subject RE: The best way to know when an index has been changed
Date Wed, 03 Aug 2005 14:09:05 GMT
Hi Luke

It's a good idea, but we need to know instantly the fail over happens.
We obtain a new instance of the index searcher every night anyway to
obtain the latest index.  When the fail over happens, the index location
is in the same place, but was wandering if there was a way to find out
if the index has changed without the database hit the first search hits
lucene after the failover.

Hope this explains the scenario more clearly.

Steve



-----Original Message-----
From: Luke [mailto:luke@lukeshannon.com] 
Sent: 03 August 2005 14:47
To: java-user@lucene.apache.org
Subject: Re: The best way to know when an index has been changed

Hi Steve;

Not sure if this would work...

Each day you could get the value from IndexReader's  getCurrentVersion
and
store it somewhere (DB or serialize it). The next day when you grab the
value again you could compare it to the stored one, if they differ you
would
know it has been replaced.

Luke

----- Original Message ----- 
From: "Steve Gaunt" <SGaunt@emeraldinsight.com>
To: <java-user@lucene.apache.org>
Sent: Wednesday, August 03, 2005 9:34 AM
Subject: The best way to know when an index has been changed


> Hi
>
> We have a web app, which keep a copy of the index searcher, then
reloads
> the index searcher every night to obtain the latest version of the
> index( as it updates every day).
> However, we have a fail over mode, which will eventually use another
> index on another server, it there anyway to know if the underlying
index
> has been replaced with another index???
>
>
> Cheers in advance
>
> Steve
>
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>



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


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

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


Mime
View raw message