I would imagine if you're doing updates all day the commit might take a long time. You could try it though and see if it works for you. Another option, which will use more disk & memory is to replicate all your data to another core just after midnight. Then update the data all day long as you please (and commit) on the new core. At the stroke of midnight the next day, swap cores. This way you can control (nearly) the exact moment the new data becomes public.
See http://wiki.apache.org/solr/CoreAdmin#SWAP James Dyer E-Commerce Systems Ingram Content Group (615) 213-4311 -----Original Message----- From: roySolr [mailto:royrutten1...@gmail.com] Sent: Friday, July 29, 2011 5:36 AM To: solr-user@lucene.apache.org Subject: Updating opinion Hello, I want some opinions for the updating process of my application. Users can edit there own data. This data will be validated and must be updated every 24 hours. I want to do this at night(0:00). Now lets say 50.000 documents are edited. The delta import will take ~20 minutes. So the indexing proces is ready at 0:20. Some data is depending on day. So the index has wrong data for 20 minutes. Now i thought i can fix this problem this way: I can do every hour a delta import without a commit. I do this 24 times and on the end of the day i do a commit and optimize the index. Is this possible? Is it faster to do the updates in parts? -- View this message in context: http://lucene.472066.n3.nabble.com/Updating-opinion-tp3209251p3209251.html Sent from the Solr - User mailing list archive at Nabble.com.
