[
https://issues.apache.org/jira/browse/SOLR-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-1324.
---------------------------------
Resolution: Duplicate
I think this is all sorted with SOLR-2700 (transaction logging)
> Persisting update processor
> ---------------------------
>
> Key: SOLR-1324
> URL: https://issues.apache.org/jira/browse/SOLR-1324
> Project: Solr
> Issue Type: New Feature
> Components: update
> Reporter: Erik Hatcher
> Priority: Minor
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
