Using the TermVectorMapper I was able to "rebuild" the contents field and after a bit of digging found that I had to remove a field before adding it back or I got strange behavior.
Thanks for your time! On Tue, Dec 20, 2011 at 5:47 PM, Trevor Watson <twat...@datassimilate.com>wrote: > Update: > > I've managed to get the information to move from one index to the other > with the exception of the file contents (you know, the important field). > The other fields are stored in the index, but I suspect that the content > field is not being moved as it is not stored, but rather save with > Field.Store.NO, Field.Index.TOKENIZED, TermVector.WITH_POSITION_**OFFSETS > > I suppose this means I could use the code that somebody gave me on here > (thanks again), for re-creating the field contents using TermVectorMapping > and then re-adding the contents field with the re-created contents. > > Is this correct that that field isn't moving over because of this? > > Thanks again > > Trevor > > > On 12/20/2011 5:14 PM, Trevor Watson wrote: > >> Hello! >> >> We currently have made a utility that writes the contents of files to a >> Lucene index and then allows the user to search the contents of these >> files. We had a client who had a job that was too large to process on a >> single computer, so we split it up amongst multiple computers and now want >> to make it a single job at the end for searching. >> >> The system has a database and the lucene index. We would like to merge >> the Documents from one index to another, but need to update the unique (per >> job) file ID that links the Lucene index to the database. >> >> Is there an easy way to update a single field then move the information >> to another index? >> >> Thanks in advance >> > > >
