mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-24 15:17:30 -04:00
42cd3433b9
Today when creating an internal test cluster, we allow the test to supply the node settings that are applied. The extension point to provide these settings has a single integer parameter, indicating the index (zero-based) of the node being constructed. This allows the test to make some decisions about the settings to return, but it is too simplistic. For example, imagine a test that wants to provide a setting, but some values for that setting are not valid on non-data nodes. Since the only information the test has about the node being constructed is its index, it does not have sufficient information to determine if the node being constructed is a non-data node or not, since this is done by the test framework externally by overriding the final settings with specific settings that dicate the roles of the node. This commit changes the test framework so that the test has information about what settings are going to be overriden by the test framework after the test provide its test-specific settings. This allows the test to make informed decisions about what values it can return to the test framework. |
||
|---|---|---|
| .. | ||
| config/discovery-ec2 | ||
| licenses | ||
| qa | ||
| src | ||
| build.gradle | ||