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?
http://wiki.apache.org/solr/SolrConfigXml#A.22Update.22_Related_Event_Listeners http://www.lucidimagination.com/solutions/webinars/mastering-the-lucene-index -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com On 5. nov. 2010, at 16.11, Markus Jelsma wrote: > Hi, > > I've got an ordinary master/slave replication set up. The master contains > several fields that are not used by the slaves but are used by processes that > interact with the master. Removing the fields from the master is not an > option. > > Well, to save disk space i'd figure i create an `ignored` fieldType and set > the > fields that are unused on the slaves to use the ignored fieldType. > > ..it doesn't work and makes perfectly sense because it's just the index files > that get copied over. > > The question, how to ignore fields with replication? > > Cheers, > -- > Markus Jelsma - CTO - Openindex > http://www.linkedin.com/in/markus17 > 050-8536600 / 06-50258350
