[SOLR-1324] Persisting update processor

• Type: New Feature
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Component/s: update
• Assignee: Unassigned
• Reporter: Erik Hatcher
• Created: 01/Aug/09 02:16
• Updated: 21/Feb/12 23:57
• Resolved: 21/Feb/12 23:57

Description

Logging this idea... A persisting update processor could be implemented to send all commands through some "persister" abstraction. One straightforward implementation could write all actions to Solr XML files on the file system.

Issues to consider: need to write files in chronological order to play them back in sequence. what about commits/delets/rollbacks? do we persist these other commands or only adds? on playback (say java -jar post.jar *.xml), need to have a way to not persist.

Need to persist the SolrInputDocument, not the Lucene document.