2 Commits

Author	SHA1	Message	Date
Igor Motov	f71c9a25a1	Check for incompatible mappings while upgrading old indices ... Conflicting mappings that were allowed before v2.0 can cause runaway shard failures on upgrade. This commit adds a check that prevents a cluster from starting if it contains such indices as well as restoring such indices from a snapshot into already running cluster. Closes #11857	2015-08-04 18:13:29 -06:00
Michael McCandless	399f0ccce9	Core: add only_ancient_segments to upgrade API, so only segments with an old Lucene version are upgraded ... This option defaults to false, because it is also important to upgrade the "merely old" segments since many Lucene improvements happen within minor releases. But you can pass true to do the minimal work necessary to upgrade to the next major Elasticsearch release. The HTTP GET upgrade request now also breaks out how many bytes of ancient segments need upgrading. Closes #10213 Closes #10540 Conflicts: dev-tools/create_bwc_index.py rest-api-spec/api/indices.upgrade.json src/main/java/org/elasticsearch/action/admin/indices/optimize/OptimizeRequest.java src/main/java/org/elasticsearch/action/admin/indices/optimize/ShardOptimizeRequest.java src/main/java/org/elasticsearch/action/admin/indices/optimize/TransportOptimizeAction.java src/main/java/org/elasticsearch/index/engine/InternalEngine.java src/test/java/org/elasticsearch/bwcompat/StaticIndexBackwardCompatibilityTest.java src/test/java/org/elasticsearch/index/engine/InternalEngineTests.java src/test/java/org/elasticsearch/rest/action/admin/indices/upgrade/UpgradeReallyOldIndexTest.java	2015-04-16 05:24:33 -04:00