Ferret talk - Dec 2006 - How to handle updates from other machine

Hi,
Right now I''m having ferret index about 1.5million documents.  I plan
on
rebuilding the index on another machine and then copying the index over
to the webserver.  I read in one of the other posts that ferret has to
reopen the index to see any new changes.  Is there a way to script this?
My frontend is a RoR app using AAF.
Thanks,
Chris

-- 
Posted via http://www.ruby-forum.com/.

A related question (apologies to Chris for jumping in on his question):

Are there any issues we should be aware of when copying indexes between
machines?  Like, can we copy to and from any pair of machines?  Or are there
binary layout/word size/Endian issues?


Schnitz

On 12/4/06, Chris Williams <cswilliams at gmail.com>
wrote:
>
> Hi,
> Right now I''m having ferret index about 1.5million documents.  I
plan on
> rebuilding the index on another machine and then copying the index over
> to the webserver.  I read in one of the other posts that ferret has to
> reopen the index to see any new changes.  Is there a way to script this?
> My frontend is a RoR app using AAF.
> Thanks,
> Chris
>
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> Ferret-talk mailing list
> Ferret-talk at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ferret-talk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/ferret-talk/attachments/20061204/374e169d/attachment-0001.html

On Mon, Dec 04, 2006 at 07:10:41PM +0100, Chris Williams
wrote:
> Hi,
> Right now I''m having ferret index about 1.5million documents.  I
plan on
> rebuilding the index on another machine and then copying the index over
> to the webserver.  I read in one of the other posts that ferret has to
> reopen the index to see any new changes.  Is there a way to script this?
> My frontend is a RoR app using AAF.
you could build a ''secret'' action in your app that triggers
the
reopening of the index. 

Or you check if your reader is reading from the current index before
using it with IndexReader#is_latest?

Jens

-- 
webit! Gesellschaft f?r neue Medien mbH          www.webit.de
Dipl.-Wirtschaftsingenieur Jens Kr?mer       kraemer at webit.de
Schnorrstra?e 76                         Tel +49 351 46766  0
D-01069 Dresden                          Fax +49 351 46766 66

I see. Doesn''t AAF just reopen the index again on the next request 
though?  I don''t mind if updates aren''t seen until the next
request
occurs...

-- 
Posted via http://www.ruby-forum.com/.

On Thu, Dec 07, 2006 at 07:32:11PM +0100, Chris Williams
wrote:
> I see. Doesn''t AAF just reopen the index again on the next request
> though?  I don''t mind if updates aren''t seen until the
next request
> occurs...
Right, aaf uses Ferret''s Ferret::I class which afair does check if 
it''s searcher looks at the most recent version of the index, so 
everything should be fine.

Jens

 

-- 
webit! Gesellschaft f?r neue Medien mbH          www.webit.de
Dipl.-Wirtschaftsingenieur Jens Kr?mer       kraemer at webit.de
Schnorrstra?e 76                         Tel +49 351 46766  0
D-01069 Dresden                          Fax +49 351 46766 66