On Fri, Nov 5, 2010 at 2:30 PM, Jan Høydahl / Cominvent <[email protected]> wrote: > > How about hooking in Andrzej's pruning tool at the postCommit event, > literally removing unused fields. I believe a "commit" is fired on the slave > by itself after every successful replication, to put > the index live. You could execute a script which prunes away the dead meat > and then call a new commit?
Well, I don't think it will work because a new commit will cause the index version on the slave to be ahead of the master which will cause Solr replication to download a full index from the master and it'd go in an infinite loop. -- Regards, Shalin Shekhar Mangar.
