mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-03-09 14:34:43 +00:00
4239ba5415
This change allows reads of our native users and roles when the template version has not been updated to match the current version. This is useful for rolling upgrades where the nodes are also being actively queried and/or indexed into. Without this, we can wreak havoc on a cluster by causing exceptions during replication, which leads to shard failures. On nodes that match the version defined in the template, write operations are allowed since we know that we are backwards compatible in terms of format but we may have added new fields and shouldn't index them until the mappings and template have been updated. As part of this, the rolling upgrade tests from core were used as the basis for a very basic set of tests for doing a rolling upgrade with x-pack. Closes elastic/elasticsearch#4126 Original commit: elastic/x-pack-elasticsearch@9be518ef00
= Elasticsearch X Plugins A set of Elastic's commercial plugins: - License - Security - Watcher - Monitoring = Setup You must checkout x-plugins and elasticsearch in the same directory as siblings. This elasticsearch checkout will be used when building x-plugins. = Build - Run unit tests: + [source, txt] ----- gradle clean test ----- - Run all tests: + [source, txt] ----- gradle clean check ----- - Run integration tests: + [source, txt] ----- gradle clean integTest ----- - Package X-Pack (wihtout running tests) + [source, txt] ----- gradle clean assemble ----- - Install X-Pack (wihtout running tests) + [source, txt] ----- gradle clean install ----- - If you don't work on the UI side of x-plugins, you can force gradle to skip building kibana by adding `xpack.kibana.build=false` to your `~/.gradle/gradle.properties`. Alternatively you add `-Pxpack.kibana.build=false` on the command line if you only want to do this on individual builds (or `-Pxpack.kibana.build=true` if you need to override having added this to your `gradle.properties`).