Hi Walter, Thanks for the response.
Commit will help to reflect changes on Box1. We are able to achieve this. We want the changes to reflect in Box2. We have two indexes. Say Box1: Master & DB has been setup. Data Import runs on this. Box2: Slave running. We want all the updates on Box1 to be merged/present in index on Box2. Both the boxes are not connected over n/w. How can be achieve this. Please let me know, if am not clear. Thanks again! Regards, Dikchant On Tue, Dec 11, 2012 at 11:22 AM, Walter Underwood <wun...@wunderwood.org>wrote: > You do not need to manage online and offline indexes. Commit when you are > done with your updates and Solr will take care of it for you. The changes > are not live until you commit. > > wunder > > On Dec 10, 2012, at 9:46 PM, Dikchant Sahi wrote: > > > Hi, > > > > How can we do delta update of offline indexes? > > > > We have the master index on which data import will be done. The index > > directory will be copied to slave machine in case of full update, through > > CD as the slave/client machine is offline. > > So, what should be the approach for getting the delta to the slave. I can > > think of two approaches. > > > > 1.Create separate indexes of the delta on the master machine, copy it to > > the slave machine and merge. Before merging the indexes on the client > > machine, delete all the updated and deleted documents in client machine > > else merge will add duplicates. So along with the index, we need to > > transfer the list of documents which has been updated/deleted. > > > > 2. Extract all the documents which has changed since a particular time in > > XML/JSON and index it in client machine. > > > > The size of indexes are huge, so we cannot rollover index everytime. > > > > Please help me with your take and challenges you see in the above > > approaches. Please suggest if you think of any other better approach. > > > > Thanks a ton! > > > > Regards, > > Dikchant > > -- > Walter Underwood > wun...@wunderwood.org > > > >
