RavenDB-1108 locking indexes when running in memory fails and test for it
RavenDB-1107 Incorrect results when calculating on multiple fields for a single Aggregate
and test for it
Add test for Transform results with include
Fixing etag synchronizer issue - when an etag needs to be persisted make sure it's committed in a single and separate batch, not as the nested one which would be committed together with the parent.
Attempt to ensure that reading/upading the LastIndexedEtag value is no longer a problem in Munin
Failing test for Lazily() bug
Merge branch 'master' of https://github.com/asapostolov/ravendb into 2.5
Fixing an issue with OrderBy & Where on the same field using lazy
WriteQueueToServer should run in a different thread
In bulk inserts ensuring snapshot after adding Etag to the document
Mark index as 'in progress' right after adding it to indexes to work inside the AbstractIndexingExecuter. This is needed for better index staleness detection to avoid false negative answers when we wait for non stale results
Fixing test
Fix a deadlock which happens when running the the AspNetSynchronizationContext or LegacyAspNetSynchronizationContext. When using with a null SynchronizationContext, as what we have in a console app, the deadlock issue not occur.
Merge branch 'master' of https://github.com/florisrobbemont/ravendb into 2.5
Merge branch '2.5' of https://github.com/fitzchak/ravendb into 2.5
Will not corrupt the SynchronizationContext
Future batch adding should be after adding already loaded docs to the prefetching queue
Prefetching behavior no longer relays on the fact the next expected etag to process should be greater exactly by 1 - it caused issues, so it's better to allow for re-indexation already indexed documents to make sure that it will never hang because of some missing consecutive etag.
Do not close the ram directory of the index when it's copied because after that, the Dispose method of the index writer calls Commit on already closed dir and the exception is thrown. This in turn caused that IndexSearcher was not recreated and gave invalid results of a query. Now we need to manually dispose the ram dir after closing the writer.
Now we don't need to mock the prefetcher