OK, sounds good. Fall will be here before you know it!
Mike
Christopher Kolstad wrote:
The only way to make this work with svn is if you can have svn
perform a
switch without doing any removal, then restart your IndexSearcher,
then do a
normal svn switch to remove the now unused files.
>
> The only way to make this work with svn is if you can have svn perform a
> switch without doing any removal, then restart your IndexSearcher, then do a
> normal svn switch to remove the now unused files. Does svn have an option
> to "switch but don't remove any removed files"? Because IndexSe
OK, got it.
The only way to make this work with svn is if you can have svn perform
a switch without doing any removal, then restart your IndexSearcher,
then do a normal svn switch to remove the now unused files. Does svn
have an option to "switch but don't remove any removed files"?
Bec
Hi.
First, thanks for the reply.
Why does SubversionUpdate require shutting down the IndexSearcher? What
> goes wrong?
>
SubversionUpdate requires shutting down the IndexSearcher in our current
implementation because the old index files are deleted in the tag we're
switching to. Sorry, just rea
Why does SubversionUpdate require shutting down the IndexSearcher?
What goes wrong?
You might want to switch instead to rsync.
A Lucene index is fundamentally write once, so, syncing changes over
should simply be copying over new files and removing now-deleted
files. You won't be able
Hi.
Currently using Lucene 2.3.2 in a tomcat webapp. We have an action
configured that performs reindexing on our staging server. However, our live
server can not reindex since it does not have the necessary dtd files to
process the xml.
To update the index on the live server we perform a subvers
