I understand the bottom line that soft commits are about visibility, hard commits are about durability. I am just trying to gain better understanding what happens under the hood... 2 more related questions you made me think of: 1. Does the NRTCachingDirectoryFactory relevant for both types of commit, or just for hard commit? 2. If soft commit does not flush - all data exists in RAM until we call hard commit? If so, using soft commit without calling hard commit could cause OOE ... ?
-- View this message in context: http://lucene.472066.n3.nabble.com/Soft-commit-and-flush-tp4091726p4093834.html Sent from the Solr - User mailing list archive at Nabble.com.
