Nhat Nguyen aa0c957a4a Do not trim unsafe commits when open readonly engine (#41041) ...

Today we always trim unsafe commits (whose max_seq_no >= global
checkpoint) before starting a read-write or read-only engine. This is
mandatory for read-write engines because they must start with the safe
commit. This is also fine for read-only engines since most of the cases
we should have exactly one commit after closing an index (trimming is a
noop). However, this is dangerous for following indices which might have
more than one commits when they are being closed.

With this change, we move the trimming logic to the ctor of InternalEngine
so we won't trim anything if we are going to open a read-only engine.

2019-04-17 10:16:12 -04:00

..

licenses

Upgrade to Lucene release 8.0.0 (#39998)

2019-03-13 18:11:50 +01:00

src

Do not trim unsafe commits when open readonly engine (#41041)

2019-04-17 10:16:12 -04:00

build.gradle

[Backport] Replace usages RandomizedTestingTask with built-in Gradle Test (#40978) (#40993)

2019-04-09 11:52:50 -07:00