Index locking fix - in order to lock the writing to an index operation you have to obtain the lock explicitly
Attempt to restore index (map-only right now) from previously stored segment file.
Merge branch 'Highlight_Test' of github.com:DanielDar/ravendb into 2.01
minor
minor
RavenDB-866 Highlights missing fragments when fragment length is too long
Recovering map indexes based on stored commit points
Merge branch 'master' of git://github.com/ayende/ravendb into preventing-index-resets
Fix alerts for periodic backup and the ui for it
handle null in secured settings
For map/reduce index regenerate the entire index from already reduced results if index failure was discovered
Add Alerts to sql replications
add unique key to periodic backups alerts
Merge branch 'master' of git://github.com/ayende/ravendb into preventing-index-resets
Avoid nesting. Better names of commit point directories
Try to index recovery operation after we failed with CheckIndexAndTryToFix
Regenerate map/reduce index in single batch with the usage of pulsing transactions.
Adding max time interval for storing index commit points
fixing build
Storing keys that were deleted after saving commit point. This will be useful in index recovery scenario
Removing keys from recovered index