Re: Best practice for updating an index when reindexing is not an option

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.

Re: Best practice for updating an index when reindexing is not an option

> > 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

Re: Best practice for updating an index when reindexing is not an option

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

Re: Best practice for updating an index when reindexing is not an option

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

Re: Best practice for updating an index when reindexing is not an option

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

Best practice for updating an index when reindexing is not an option

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

Updating an Index

Hi all, I am new to lucene. I would like to know if there can be any performance issues if we update the boost of a document often. Does this scale linearly with index size?

Re: updating an index... with existing documents ?

On Jul 28, 2005, at 8:36 AM, Paul Libbrecht wrote: Dare I ask wether this implies that the fields are stored ? I don't quite understand. The "reconstruct" feature of Luke (and thus the code you can borrow from) does not require that fields are stored - it pulls the indexed terms from the

Re: updating an index... with existing documents ?

Dare I ask wether this implies that the fields are stored ? thanks paul Le 28 juil. 05, à 14:26, Erik Hatcher a écrit : It is possible to reconstruct a document from the index, but it is a potentially lossy proposition, since stemming and other manglings might have gone on. Look at Luke and

Re: updating an index... with existing documents ?

Paul, It is possible to reconstruct a document from the index, but it is a potentially lossy proposition, since stemming and other manglings might have gone on. Look at Luke and see how it does it (you can "reconstruct and edit" a document from its UI). Erik On Jul 28, 2005, at 5:37

updating an index... with existing documents ?

hi, My mission is currently to update an index by marking adding a flag field on some documents. For this, I seem to have the only following possibility: - search for the documents in question, store them, filter them - modify the documents in accordance - delete the modified documents - put b