root
/
elasticsearch
mirror of https://github.com/elastic/elasticsearch.git
1
0
Fork 0
Code Issues Actions 1 Packages Projects Releases Wiki Activity
elasticsearch/rest-api-spec/build.gradle

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

249 lines
14 KiB
Groovy
Raw Normal View History

Mute rest-api-spec compatibility tests on Windows
2021-02-25 04:34:44 +08:00
import org.elasticsearch.gradle.OS
Add build plugin to rest-api-spec to properly generate pom (#59142) The build plugin is still necessary to generate the POM file. This commit adds the build plugin plugin back to the rest-api-spec project. It was recently removed as it was thought to be unnecessary.
2020-07-07 22:58:07 +08:00
apply plugin: 'elasticsearch.build'
Move publishing configuration to a separate plugin (#56727) This is another part of the breakup of the massive BuildPlugin. This PR moves the code for configuring publications to a separate plugin. Most of the time these publications are jar files, but this also supports the zip publication we have for integ tests.
2020-05-15 09:56:59 +08:00
apply plugin: 'elasticsearch.publish'
Add Watcher to available rest resources (#53620) Prior to this commit Watcher explicitly copied test between two projects with a copy task. This commit removes the explicit copy in favor of adding the Watcher tests to the available restResources that may be copied between projects. This is how inter-project dependencies should be modeled. However, only Watcher is included here since it is (currently) the only project with inter-project test dependencies. Note - this re-introduces: commit: 4f48e053f92b2ae7677a2e2ba0e5464ede7128d1 with some additional fixes.
2020-03-18 22:08:13 +08:00
apply plugin: 'elasticsearch.rest-resources'
Validate REST specs against schema (#55117) A JSON schema was recently introduced for the REST API specification. #54252 This PR introduces a 3rd party validation tool to ensure that the REST specification conforms to the schema. The task is applied to the 3 projects that contain REST API specifications. The plugin wires this task into the precommit commit task, and should be considered as part of the public API for the build tools for any plugin developer to contribute their plugin's specification. An ignore parameter has been introduced for the task to allow specific file to be ignored from the validation. The ignored files in this PR will soon get issues logged and a link so they can be fixed. Closes #54314
2020-04-22 07:18:18 +08:00
apply plugin: 'elasticsearch.validate-rest-spec'
Introduce simple public yaml-rest-test plugin (#76554) This introduces a basic public yaml rest test plugin that is supposed to be used by external elasticsearch plugin authors. This is driven by #76215 - Rename yaml-rest-test to intern-yaml-rest-test - Use public yaml plugin in example plugins Co-authored-by: Mark Vieira <portugee@gmail.com>
2021-08-31 14:45:52 +08:00
apply plugin: 'elasticsearch.internal-yaml-rest-test'
Apply yaml-rest-compat-test to rest-api-spec (#69462)
2021-02-24 02:15:53 +08:00
apply plugin: 'elasticsearch.yaml-rest-compat-test'
Enable installing the rest-api-spec artifact Running `gradle install` on the rest-api-spec fails because there is no available install task. This change applies the nexus plugin so that we can install and should also enable publishing as part of the uploadArchives task.
2016-04-13 23:26:47 +08:00
Create plugin for yamlTest task (#56841) This commit creates a new Gradle plugin to provide a separate task name and source set for running YAML based REST tests. The only project converted to use the new plugin in this PR is distribution/archives/integ-test-zip. For which the testing has been moved to :rest-api-spec since it makes the most sense and it avoids a small but awkward change to the distribution plugin. The remaining cases in modules, plugins, and x-pack will be handled in followups. This plugin is distinctly different from the plugin introduced in #55896 since the YAML REST tests are intended to be black box tests over HTTP. As such they should not (by default) have access to the classpath for that which they are testing. The YAML based REST tests will be moved to separate source sets (yamlRestTest). The which source is the target for the test resources is dependent on if this new plugin is applied. If it is not applied, it will default to the test source set. Further, this introduces a breaking change for plugin developers that use the YAML testing framework. They will now need to either use the new source set and matching task, or configure the rest resources to use the old "test" source set that matches the old integTest task. (The former should be preferred). As part of this change (which is also breaking for plugin developers) the rest resources plugin has been removed from the build plugin and now requires either explicit application or application via the new YAML REST test plugin. Plugin developers should be able to fix the breaking changes to the YAML tests by adding apply plugin: 'elasticsearch.yaml-rest-test' and moving the YAML tests under a yamlRestTest folder (instead of test)
2020-07-07 01:13:01 +08:00
restResources {
restTests {
includeCore '*'
}
}
Smarter copying of the rest specs and tests (#52114) This PR addresses the unnecessary copying of the rest specs and allows for better semantics for which specs and tests are copied. By default the rest specs will get copied if the project applies `elasticsearch.standalone-rest-test` or `esplugin` and the project has rest tests or you configure the custom extension `restResources`. This PR also removes the need for dozens of places where the x-pack specs were copied by supporting copying of the x-pack rest specs too. The plugin/task introduced here can also copy the rest tests to the local project through a similar configuration. The new plugin/task allows a user to minimize the surface area of which rest specs are copied. Per project can be configured to include only a subset of the specs (or tests). Configuring a project to only copy the specs when actually needed should help with build cache hit rates since we can better define what is actually in use. However, project level optimizations for build cache hit rates are not included with this PR. Also, with this PR you can no longer use the includePackaged flag on integTest task. The following items are included in this PR: * new plugin: `elasticsearch.rest-resources` * new tasks: CopyRestApiTask and CopyRestTestsTask - performs the copy * new extension 'restResources' ``` restResources { restApi { includeCore 'foo' , 'bar' //will include the core specs that start with foo and bar includeXpack 'baz' //will include x-pack specs that start with baz } restTests { includeCore 'foo', 'bar' //will include the core tests that start with foo and bar includeXpack 'baz' //will include the x-pack tests that start with baz } } ```
2020-02-26 08:46:32 +08:00
Consolidate REST API specifications and publish under Apache 2.0 license (#70036)
2021-03-27 07:20:14 +08:00
// REST API specifications are published under the Apache 2.0 License
Move public build api into included build (#72861) This moves the public build api and plugins into a separete included build called 'build-tools' and we removed the duplication of included buildSrc twice (2nd import as build-tools). The elasticsearch internal build logic is kept in build-tools-internal as included build which allows us better handling of this project that its just being an buildSrc project (e.g. we can reference tasks directly from the root build etc.) Convention logic applied to both projects will live in a new build-conventions project.
2021-06-01 17:19:30 +08:00
ext.projectLicenses.set(['The Apache Software License, Version 2.0': 'http://www.apache.org/licenses/LICENSE-2.0'])
Consolidate REST API specifications and publish under Apache 2.0 license (#70036)
2021-03-27 07:20:14 +08:00
ext.licenseFile = rootProject.file('licenses/APACHE-LICENSE-2.0.txt')
Introduce simple public yaml-rest-test plugin (#76554) This introduces a basic public yaml rest test plugin that is supposed to be used by external elasticsearch plugin authors. This is driven by #76215 - Rename yaml-rest-test to intern-yaml-rest-test - Use public yaml plugin in example plugins Co-authored-by: Mark Vieira <portugee@gmail.com>
2021-08-31 14:45:52 +08:00
configurations {
// configuration to make use by external yaml rest test plugin in our examples
// easy and efficient
basicRestSpecs {
attributes {
attribute(org.gradle.api.internal.artifacts.ArtifactAttributes.ARTIFACT_FORMAT, ArtifactTypeDefinition.DIRECTORY_TYPE)
}
}
}
Smarter copying of the rest specs and tests (#52114) This PR addresses the unnecessary copying of the rest specs and allows for better semantics for which specs and tests are copied. By default the rest specs will get copied if the project applies `elasticsearch.standalone-rest-test` or `esplugin` and the project has rest tests or you configure the custom extension `restResources`. This PR also removes the need for dozens of places where the x-pack specs were copied by supporting copying of the x-pack rest specs too. The plugin/task introduced here can also copy the rest tests to the local project through a similar configuration. The new plugin/task allows a user to minimize the surface area of which rest specs are copied. Per project can be configured to include only a subset of the specs (or tests). Configuring a project to only copy the specs when actually needed should help with build cache hit rates since we can better define what is actually in use. However, project level optimizations for build cache hit rates are not included with this PR. Also, with this PR you can no longer use the includePackaged flag on integTest task. The following items are included in this PR: * new plugin: `elasticsearch.rest-resources` * new tasks: CopyRestApiTask and CopyRestTestsTask - performs the copy * new extension 'restResources' ``` restResources { restApi { includeCore 'foo' , 'bar' //will include the core specs that start with foo and bar includeXpack 'baz' //will include x-pack specs that start with baz } restTests { includeCore 'foo', 'bar' //will include the core tests that start with foo and bar includeXpack 'baz' //will include the x-pack tests that start with baz } } ```
2020-02-26 08:46:32 +08:00
artifacts {
Introduce simple public yaml-rest-test plugin (#76554) This introduces a basic public yaml rest test plugin that is supposed to be used by external elasticsearch plugin authors. This is driven by #76215 - Rename yaml-rest-test to intern-yaml-rest-test - Use public yaml plugin in example plugins Co-authored-by: Mark Vieira <portugee@gmail.com>
2021-08-31 14:45:52 +08:00
basicRestSpecs(new File(projectDir, "src/main/resources"))
Smarter copying of the rest specs and tests (#52114) This PR addresses the unnecessary copying of the rest specs and allows for better semantics for which specs and tests are copied. By default the rest specs will get copied if the project applies `elasticsearch.standalone-rest-test` or `esplugin` and the project has rest tests or you configure the custom extension `restResources`. This PR also removes the need for dozens of places where the x-pack specs were copied by supporting copying of the x-pack rest specs too. The plugin/task introduced here can also copy the rest tests to the local project through a similar configuration. The new plugin/task allows a user to minimize the surface area of which rest specs are copied. Per project can be configured to include only a subset of the specs (or tests). Configuring a project to only copy the specs when actually needed should help with build cache hit rates since we can better define what is actually in use. However, project level optimizations for build cache hit rates are not included with this PR. Also, with this PR you can no longer use the includePackaged flag on integTest task. The following items are included in this PR: * new plugin: `elasticsearch.rest-resources` * new tasks: CopyRestApiTask and CopyRestTestsTask - performs the copy * new extension 'restResources' ``` restResources { restApi { includeCore 'foo' , 'bar' //will include the core specs that start with foo and bar includeXpack 'baz' //will include x-pack specs that start with baz } restTests { includeCore 'foo', 'bar' //will include the core tests that start with foo and bar includeXpack 'baz' //will include the x-pack tests that start with baz } } ```
2020-02-26 08:46:32 +08:00
restSpecs(new File(projectDir, "src/main/resources/rest-api-spec/api"))
Consolidate REST API specifications and publish under Apache 2.0 license (#70036)
2021-03-27 07:20:14 +08:00
restTests(new File(projectDir, "src/yamlRestTest/resources/rest-api-spec/test"))
Smarter copying of the rest specs and tests (#52114) This PR addresses the unnecessary copying of the rest specs and allows for better semantics for which specs and tests are copied. By default the rest specs will get copied if the project applies `elasticsearch.standalone-rest-test` or `esplugin` and the project has rest tests or you configure the custom extension `restResources`. This PR also removes the need for dozens of places where the x-pack specs were copied by supporting copying of the x-pack rest specs too. The plugin/task introduced here can also copy the rest tests to the local project through a similar configuration. The new plugin/task allows a user to minimize the surface area of which rest specs are copied. Per project can be configured to include only a subset of the specs (or tests). Configuring a project to only copy the specs when actually needed should help with build cache hit rates since we can better define what is actually in use. However, project level optimizations for build cache hit rates are not included with this PR. Also, with this PR you can no longer use the includePackaged flag on integTest task. The following items are included in this PR: * new plugin: `elasticsearch.rest-resources` * new tasks: CopyRestApiTask and CopyRestTestsTask - performs the copy * new extension 'restResources' ``` restResources { restApi { includeCore 'foo' , 'bar' //will include the core specs that start with foo and bar includeXpack 'baz' //will include x-pack specs that start with baz } restTests { includeCore 'foo', 'bar' //will include the core tests that start with foo and bar includeXpack 'baz' //will include the x-pack tests that start with baz } } ```
2020-02-26 08:46:32 +08:00
}
Add build plugin to rest-api-spec to properly generate pom (#59142) The build plugin is still necessary to generate the POM file. This commit adds the build plugin plugin back to the rest-api-spec project. It was recently removed as it was thought to be unnecessary.
2020-07-07 22:58:07 +08:00
Add support for missing value fetchers. (#63515) This PR implements value fetching for the following field types: * `text` phrase and prefix subfields * `search_as_you_type`, plus its subfields * `token_count`, which is implemented by fetching doc values Supporting these types helps ensure that retrieving all fields through `"fields": ["*"]` doesn't fail because of unsupported value fetchers.
2020-10-13 04:57:29 +08:00
testClusters.all {
module ':modules:mapper-extras'
}
Consolidate REST API specifications and publish under Apache 2.0 license (#70036)
2021-03-27 07:20:14 +08:00
tasks.named("test").configure { enabled = false }
tasks.named("jarHell").configure { enabled = false }
Update task names for rest compatiblity (#75267) This commit updates two task names: ``` yamlRestCompatTest -> yamlRestTestV7CompatTest transformV7RestTests -> yamlRestTestV7CompatTransform ``` `7` is the N-1 version and calculated, such that when `8` is N-1 version the task names will be `yamlRestTestV8CompatTest` and `yamlRestTestV8CompatTransform` The motivation for `yamlRestCompatTest -> yamlRestTestV7CompatTest` is that many projects have configured `yamlRestCompatTest` but that configuration is specific to the N-1 version. For example, if we blacklist tests when running compatibility with v7, we don't also want to blacklist those tests when running compatibility with v8. By introducing a version-specific identifier in the name, the task will not even exist when bumping the version creating the need to (correctly) remove the version-specific condition. The motivation for `transformV7RestTests -> yamlRestTestV7CompatTransform` is to provide more consistent naming. The idea behind the naming is the main task people are likely familiar with is : `yamlRestTest` so we will use that as a base. `yamlRestTestV7CompatTest` to run the version-specific compat tests `yamlRestTestV7CompatTransform` to run the version-specific transformations for the compat tests CI should be un-effected since since we introduced a lifecycle task name `checkRestCompat` which is what CI should be configured to use.
2021-09-04 00:26:11 +08:00
tasks.named("yamlRestTestV7CompatTest").configure {
[Rest Api Compatibility] Clean up blocklist (#76179) v7compatibilityNotSupportedTests was introduced to make it easier to track tests that have been identified as not needing compatible changes and those that still need to be checked. We have checked all tests now and the separate list is no longer needed. relates #51816 relates #73912
2021-08-19 16:09:46 +08:00
systemProperty 'tests.rest.blacklist', [
// Cat API are meant to be consumed by humans, so will not be supported by Compatible REST API
'cat*/*/*',
// type information about the type is removed and not passed down. The logic to check for this is also removed.
'delete/70_mix_typeless_typeful/DELETE with typeless API on an index that has types',
// WILL NOT BE FIXED - failing due to not recognising missing type (the type path param is ignored)
'get/100_mix_typeless_typeful/GET with typeless API on an index that has types',
// type information about the type is removed and not passed down. The logic to check for this is also removed.
'indices.create/20_mix_typeless_typeful/Implicitly create a typed index while there is a typeless template',
'indices.create/20_mix_typeless_typeful/Implicitly create a typeless index while there is a typed template',
//
// This test returns test_index.mappings:{} when {} was expected. difference between 20_missing_field and 21_missing_field_with_types?
'indices.get_field_mapping/21_missing_field_with_types/Return empty object if field doesn\'t exist, but type and index do',
// The information about the type is not present in the index. hence it cannot know if the type exist or not.
'indices.get_field_mapping/30_missing_type/Raise 404 when type doesn\'t exist',
// The information about the type is not present in the index. hence it cannot know if the type exist or not.
'indices.get_mapping/20_missing_type/Existent and non-existent type returns 404 and the existing type',
'indices.get_mapping/20_missing_type/Existent and non-existent types returns 404 and the existing type',
'indices.get_mapping/20_missing_type/No type matching pattern returns 404',
'indices.get_mapping/20_missing_type/Non-existent type returns 404',
'indices.get_mapping/20_missing_type/Type missing when no types exist',
//
// The information about the type is not present in the index. hence it cannot know if the type was already used or not
'indices.put_mapping/20_mix_typeless_typeful/PUT mapping with _doc on an index that has types',
'indices.put_mapping/20_mix_typeless_typeful/PUT mapping with typeless API on an index that has types',
// there is a small distinction between empty mappings and no mappings at all. The code to implement this test was refactored #54003
// field search on _type field- not implementing. The data for _type is considered incorrect in this search
'search/160_exists_query/Test exists query on _type field',
//type information is not stored, hence the the index will be found
'termvectors/50_mix_typeless_typeful/Term vectors with typeless API on an index that has types',
// mget - these use cases are no longer valid, because we always default to _doc.
// This mean test cases where there is assertion on not finging by type won't work
'mget/11_default_index_type/Default index/type',
'mget/16_basic_with_types/Basic multi-get',
// asserting about type not found won't work as we ignore the type information
'explain/40_mix_typeless_typeful/Explain with typeless API on an index that has types',
// translog settings removal is not supported under compatible api
'indices.stats/20_translog/Translog retention settings are deprecated',
'indices.stats/20_translog/Translog retention without soft_deletes',
'indices.stats/20_translog/Translog stats on closed indices without soft-deletes',
[Rest Api Compatibility] Enable tests after types and cat api fixed (#75179) Some tests are fixed after typed api is available with compatible api. Also cat api returning text fixed some tests relates #51816
2021-07-14 14:37:38 +08:00
[Rest Api Compatibility] Clean up blocklist (#76179) v7compatibilityNotSupportedTests was introduced to make it easier to track tests that have been identified as not needing compatible changes and those that still need to be checked. We have checked all tests now and the separate list is no longer needed. relates #51816 relates #73912
2021-08-19 16:09:46 +08:00
// upgrade api will only get a dummy endpoint returning an exception suggesting to use _reindex
'indices.upgrade/*/*',
[Rest Api Compatibility] Enable tests after types and cat api fixed (#75179) Some tests are fixed after typed api is available with compatible api. Also cat api returning text fixed some tests relates #51816
2021-07-14 14:37:38 +08:00
Update task names for rest compatiblity (#75267) This commit updates two task names: ``` yamlRestCompatTest -> yamlRestTestV7CompatTest transformV7RestTests -> yamlRestTestV7CompatTransform ``` `7` is the N-1 version and calculated, such that when `8` is N-1 version the task names will be `yamlRestTestV8CompatTest` and `yamlRestTestV8CompatTransform` The motivation for `yamlRestCompatTest -> yamlRestTestV7CompatTest` is that many projects have configured `yamlRestCompatTest` but that configuration is specific to the N-1 version. For example, if we blacklist tests when running compatibility with v7, we don't also want to blacklist those tests when running compatibility with v8. By introducing a version-specific identifier in the name, the task will not even exist when bumping the version creating the need to (correctly) remove the version-specific condition. The motivation for `transformV7RestTests -> yamlRestTestV7CompatTransform` is to provide more consistent naming. The idea behind the naming is the main task people are likely familiar with is : `yamlRestTest` so we will use that as a base. `yamlRestTestV7CompatTest` to run the version-specific compat tests `yamlRestTestV7CompatTransform` to run the version-specific transformations for the compat tests CI should be un-effected since since we introduced a lifecycle task name `checkRestCompat` which is what CI should be configured to use.
2021-09-04 00:26:11 +08:00
[Rest Api Compatibility] Clean up blocklist (#76179) v7compatibilityNotSupportedTests was introduced to make it easier to track tests that have been identified as not needing compatible changes and those that still need to be checked. We have checked all tests now and the separate list is no longer needed. relates #51816 relates #73912
2021-08-19 16:09:46 +08:00
'search.aggregation/20_terms/*profiler*', // The profiler results aren't backwards compatible.
'search.aggregation/370_doc_count_field/Test filters agg with doc_count', // Uses profiler for assertions which is not backwards compatible
[Rest Api Compatibility] Enable tests after types and cat api fixed (#75179) Some tests are fixed after typed api is available with compatible api. Also cat api returning text fixed some tests relates #51816
2021-07-14 14:37:38 +08:00
[Rest Api Compatibility] Clean up blocklist (#76179) v7compatibilityNotSupportedTests was introduced to make it easier to track tests that have been identified as not needing compatible changes and those that still need to be checked. We have checked all tests now and the separate list is no longer needed. relates #51816 relates #73912
2021-08-19 16:09:46 +08:00
'indices.create/10_basic/Create index without soft deletes', //Make soft-deletes mandatory in 8.0 #51122 - settings changes are note supported in Rest Api compatibility
[Rest Api Compatibility] Do not return _doc for empty mappings in template (#75448) Previously the compatibility layer was always returning an _doc in mappings for get template. This commit does not return _doc in empty mappings. Returning just {} empty object (v7 and v8 behaviour) also moving term lookups tests which are already fixed (relates #74544) relates #70966 relates main meta issue #51816 relates types removal meta #54160
2021-07-19 19:21:00 +08:00
[Rest Api Compatibility] Clean up blocklist (#76179) v7compatibilityNotSupportedTests was introduced to make it easier to track tests that have been identified as not needing compatible changes and those that still need to be checked. We have checked all tests now and the separate list is no longer needed. relates #51816 relates #73912
2021-08-19 16:09:46 +08:00
'field_caps/30_filter/Field caps with index filter', //behaviour change after #63692 4digits dates are parsed as epoch and in quotes as year
[Rest Api Compatibility] Typed query (#75453) Type query support was removed in #47207. This query will throw an exception in v7 rest api compatibility indicating that the support was removed + deprecation warnings. In v8 it will not be available and error about type query being not found will be returned. relates main meta issue #51816 relates types removal meta #54160
2021-08-03 21:20:34 +08:00
[Rest Api Compatibility] Clean up blocklist (#76179) v7compatibilityNotSupportedTests was introduced to make it easier to track tests that have been identified as not needing compatible changes and those that still need to be checked. We have checked all tests now and the separate list is no longer needed. relates #51816 relates #73912
2021-08-19 16:09:46 +08:00
'indices.forcemerge/10_basic/Check deprecation warning when incompatible only_expunge_deletes and max_num_segments values are both set', //#44761 bug fix,
[Rest Api Compatibility] CommonTermsQuery and cutoff_frequency param (#75896) Previously removed in #42654. The query and the parameter won't work under rest api compatibility and an exception with a message is returned advising that just use of match/multi_match is enough relates #51816
2021-08-05 21:14:28 +08:00
[Rest Api Compatibility] Clean up blocklist (#76179) v7compatibilityNotSupportedTests was introduced to make it easier to track tests that have been identified as not needing compatible changes and those that still need to be checked. We have checked all tests now and the separate list is no longer needed. relates #51816 relates #73912
2021-08-19 16:09:46 +08:00
'search/340_type_query/type query', //#47207 type query throws exception in compatible mode
'search.aggregation/200_top_hits_metric/top_hits aggregation with sequence numbers', // #42809 the use nested path and filter sort throws an exception
'search/310_match_bool_prefix/multi_match multiple fields with cutoff_frequency throws exception', //#42654 cutoff_frequency, common terms are not supported. Throwing an exception
].join(',')
Apply yaml-rest-compat-test to rest-api-spec (#69462)
2021-02-24 02:15:53 +08:00
}
[REST Compatible API] Typed endpoints for Index and Get APIs (#69131) The types removal effort has removed the type from Index API in #47671 and from Get API in #46587 This commit allows to use 'typed' endpoints for the both Index and Get APIs relates compatible types-removal meta issue #54160
2021-03-23 17:59:21 +08:00
Update task names for rest compatiblity (#75267) This commit updates two task names: ``` yamlRestCompatTest -> yamlRestTestV7CompatTest transformV7RestTests -> yamlRestTestV7CompatTransform ``` `7` is the N-1 version and calculated, such that when `8` is N-1 version the task names will be `yamlRestTestV8CompatTest` and `yamlRestTestV8CompatTransform` The motivation for `yamlRestCompatTest -> yamlRestTestV7CompatTest` is that many projects have configured `yamlRestCompatTest` but that configuration is specific to the N-1 version. For example, if we blacklist tests when running compatibility with v7, we don't also want to blacklist those tests when running compatibility with v8. By introducing a version-specific identifier in the name, the task will not even exist when bumping the version creating the need to (correctly) remove the version-specific condition. The motivation for `transformV7RestTests -> yamlRestTestV7CompatTransform` is to provide more consistent naming. The idea behind the naming is the main task people are likely familiar with is : `yamlRestTest` so we will use that as a base. `yamlRestTestV7CompatTest` to run the version-specific compat tests `yamlRestTestV7CompatTransform` to run the version-specific transformations for the compat tests CI should be un-effected since since we introduced a lifecycle task name `checkRestCompat` which is what CI should be configured to use.
2021-09-04 00:26:11 +08:00
tasks.named("yamlRestTestV7CompatTransform").configure({ task ->
[Rest Api Compatibility] transformations for keys in match and length (#72156)
2021-05-04 21:56:37 +08:00
task.replaceValueInMatch("_type", "_doc")
[REST Compatible API] Typed endpoints for Index and Get APIs (#69131) The types removal effort has removed the type from Index API in #47671 and from Get API in #46587 This commit allows to use 'typed' endpoints for the both Index and Get APIs relates compatible types-removal meta issue #54160
2021-03-23 17:59:21 +08:00
task.addAllowedWarningRegex("\\[types removal\\].*")
[Rest Api Compatibility] transformations for keys in match and length (#72156)
2021-05-04 21:56:37 +08:00
task.replaceValueInMatch("nodes.\$node_id.roles.8", "ml", "node_info role test")
task.replaceValueInMatch("nodes.\$node_id.roles.9", "remote_cluster_client", "node_info role test")
Re-enable BWC tests after migrating ML roles This commit reenables the BWC tests after the ML roles were migrated to server. During the course of that work, the BWC tests were disabled pending that work being backported to 7.x. Now that that work is not going to be backported to 7.x, instead we apply some permanent transformations to the 7.x assertions run against ES in the REST compatibility tests.
2021-04-08 07:40:53 +08:00
task.removeMatch("nodes.\$node_id.roles.10", "node_info role test")
[Rest Compatible Api] include_type_name parameter (#70966) This commit allows to use the include_type_name parameter with the compatible rest api. The support for include_type_name was previously removed in #48632 relates #51816 types removal meta issue #54160
2021-04-19 21:21:24 +08:00
task.replaceIsTrue("test_index.mappings.type_1", "test_index.mappings._doc")
[Rest API Compatibility] Typed endpoints for Put and Get Mapping and get field mappings (#71721) Implements a V7 compatible typed endpoints for REST put and get mapping endpoints. Also for Get Field Mappings endpoints. retrofits the REST layer change removed in #41676 relates main meta issue #51816 relates types removal issue #54160
2021-05-10 16:25:48 +08:00
//override for indices.get and indices.create
//task.replaceIsFalse("test_index.mappings.type_1", "test_index.mappings._doc")
//overrides for indices.create/20_mix_typeless_typeful
task.replaceIsFalse("test-1.mappings._doc","false", "Create a typed index while there is a typeless template")
task.replaceIsFalse("test-1.mappings._doc","false", "Create a typeless index while there is a typed template")
task.replaceIsTrue("test-1.mappings.my_type", "test-1.mappings._doc")
task.replaceIsTrue("test-1.mappings.my_type.properties.foo", "test-1.mappings._doc.properties.foo")
task.replaceIsTrue("test-1.mappings.my_type.properties.bar", "test-1.mappings._doc.properties.bar")
// overrides for indices.get_field_mapping
task.replaceKeyInLength("test_index.mappings.test_type.text.mapping.text.type",
"test_index.mappings._doc.text.mapping.text.type"
)
task.replaceKeyInMatch("test_index.mappings.test_type.text.mapping.text.analyzer",
"test_index.mappings._doc.text.mapping.text.analyzer"
)
task.replaceKeyInMatch("test_index.mappings.test_type.t1.full_name",
"test_index.mappings._doc.t1.full_name"
)
task.replaceKeyInMatch("test_index.mappings.test_type.t2.full_name",
"test_index.mappings._doc.t2.full_name"
)
task.replaceKeyInMatch("test_index.mappings.test_type.obj\\.t1.full_name",
"test_index.mappings._doc.obj\\.t1.full_name"
)
task.replaceKeyInMatch("test_index.mappings.test_type.obj\\.i_t1.full_name",
"test_index.mappings._doc.obj\\.i_t1.full_name"
)
task.replaceKeyInMatch("test_index.mappings.test_type.obj\\.i_t3.full_name",
"test_index.mappings._doc.obj\\.i_t3.full_name"
)
task.replaceKeyInLength("test_index.mappings.test_type",
"test_index.mappings._doc"
)
task.replaceKeyInMatch("test_index_2.mappings.test_type_2.t1.full_name",
"test_index.mappings._doc.t1.full_name"
)
task.replaceKeyInMatch("test_index_2.mappings.test_type_2.t2.full_name",
"test_index.mappings._doc.t2.full_name"
)
task.replaceKeyInLength("test_index_2.mappings.test_type_2",
"test_index.mappings._doc"
)
task.replaceKeyInMatch("test_index.mappings.test_type.text.mapping.text.type",
"test_index.mappings._doc.text.mapping.text.type"
)
// overrides for indices.put_mapping/11_basic_with_types
task.replaceKeyInMatch("test_index.mappings.test_type.properties.text1.type",
"test_index.mappings._doc.properties.text1.type"
)
task.replaceKeyInMatch("test_index.mappings.test_type.properties.text1.analyzer",
"test_index.mappings._doc.properties.text1.analyzer"
)
task.replaceKeyInMatch("test_index.mappings.test_type.properties.text2.type",
"test_index.mappings._doc.properties.text2.type"
)
task.replaceKeyInMatch("test_index.mappings.test_type.properties.text2.analyzer",
"test_index.mappings._doc.properties.text2.analyzer"
)
task.replaceKeyInMatch("test_index.mappings.test_type.properties.subfield.properties.text3.type",
"test_index.mappings._doc.properties.subfield.properties.text3.type"
)
task.replaceKeyInMatch("test_index.mappings.test_type.properties.text1.fields.text_raw.type",
"test_index.mappings._doc.properties.text1.fields.text_raw.type"
)
// overrides for indices.put_mapping/all_path_options_with_types
task.replaceKeyInMatch("test_index1.mappings.test_type.properties.text.type",
"test_index1.mappings._doc.properties.text.type"
)
task.replaceKeyInMatch("test_index1.mappings.test_type.properties.text.analyzer",
"test_index1.mappings._doc.properties.text.analyzer"
)
task.replaceKeyInMatch("test_index2.mappings.test_type.properties.text.type",
"test_index2.mappings._doc.properties.text.type"
)
task.replaceKeyInMatch("test_index2.mappings.test_type.properties.text.analyzer",
"test_index2.mappings._doc.properties.text.analyzer"
)
task.replaceKeyInMatch("foo.mappings.test_type.properties.text.type",
"foo.mappings._doc.properties.text.type"
)
task.replaceKeyInMatch("foo.mappings.test_type.properties.text.analyzer",
"foo.mappings._doc.properties.text.analyzer"
)
// overrides for indices.get_mapping
task.replaceIsTrue("test_1.mappings.doc", "test_1.mappings._doc")
task.replaceIsTrue("test_2.mappings.doc", "test_2.mappings._doc")
[Rest Api Compatibility] Typed endpoint for multiget api (#73878) Retrofits typed api for M-get api removed in #46587 relates #51816
2021-06-09 21:19:56 +08:00
// overrides for mget
task.replaceValueInMatch("docs.0._type", "_doc" , "Basic multi-get") // index found, but no doc
task.replaceValueInMatch("docs.0._type", "_doc", "Default index/type")
task.replaceValueInMatch("docs.0._type", "_doc", "Non-existent index")
task.replaceValueInMatch("docs.0._type", "_doc", "Missing metadata")
task.replaceValueInMatch("docs.0._type", "_doc", "Multi Get with alias that resolves to multiple indices")
task.replaceValueInMatch("docs.1._type", "_doc", "Multi Get with alias that resolves to multiple indices")
task.replaceValueInMatch("docs.2._type", "_doc", "Multi Get with alias that resolves to multiple indices")
task.replaceValueInMatch("docs.0._type", "_doc", "IDs")
task.replaceValueInMatch("docs.1._type", "_doc", "IDs")
task.replaceValueInMatch("docs.2._type", "_doc", "Routing")
[Rest Api Compatibility] Typed indexing stats (#74181) the per type indexing stats is simplified and when _types is requested it will return total stats for the index repeated under types/_doc/ the removal #47203 relates main meta issue #51816 relates types removal issue #54160
2021-06-17 20:21:21 +08:00
//overrides for indices.stats
//TODO fix to remove the below match
task.replaceKeyInMatch("_all.primaries.indexing.types.baz.index_total",
"_all.primaries.indexing.types._doc.index_total"
)
task.replaceKeyInMatch("_all.primaries.indexing.types.bar.index_total",
"_all.primaries.indexing.types._doc.index_total"
)
task.replaceValueInMatch("_all.primaries.indexing.types._doc.index_total", 2)
[Rest Api Compatibility] Allow transforming warnings per test (#75187) Warning related transformations missed the possibility to apply per single test only. Also a warning changed in #67158 for indices.close so this PR also applies the transformation for 7.x test relates #51816
2021-07-15 16:50:42 +08:00
//override for "indices.open/10_basic/?wait_for_active_shards default is deprecated" and "indices.open/10_basic/?wait_for_active_shards=index-setting"
task.addAllowedWarningRegexForTest("\\?wait_for_active_shards=index-setting is now the default behaviour.*", "?wait_for_active_shards=index-setting")
task.removeWarningForTest("the default value for the ?wait_for_active_shards parameter will change from '0' to 'index-setting' in version 8; " +
"specify '?wait_for_active_shards=index-setting' to adopt the future default behaviour, or '?wait_for_active_shards=0' to preserve today's behaviour"
, "?wait_for_active_shards default is deprecated")
[Rest Api Compatibility] Voting config exclusion exception message (#75406) the exception message has changed in #55291. This is not covered by rest api compatibility, so no need to return the old message for v7 requests. This commit adds a transformation to allow for the 7.x test to pass with a new exception message relates #51816
2021-07-26 22:42:38 +08:00
// override for exception message change in #55291 tests cluster.voting_config_exclusions/10_basic/
// 'Throw exception when adding voting config exclusion and specifying both node_ids and node_names',
// 'Throw exception when adding voting config exclusion without specifying nodes',
task.replaceValueTextByKeyValue("catch",
'/Please set node identifiers correctly. One and only one of \\[node_name\\], \\[node_names\\] and \\[node_ids\\] has to be set/',
'/You must set \\[node_names\\] or \\[node_ids\\] but not both/')
[Rest Api Compatibility] Deprecate the use of synced flush (#75372) synced flush is going to be replaced by flush. This commit allows to synced_flush api only in v7 compatibility mode. Worth noting - sync_id is gone and won't be available in v7 responses from indices.stats relates removal pr #50882 relates #51816
2021-07-28 20:17:49 +08:00
// sync_id is no longer available in SegmentInfos.userData // "indices.flush/10_basic/Index synced flush rest test"
task.replaceIsTrue("indices.testing.shards.0.0.commit.user_data.sync_id", "indices.testing.shards.0.0.commit.user_data")
[REST Compatible API] Typed endpoints for Index and Get APIs (#69131) The types removal effort has removed the type from Index API in #47671 and from Get API in #46587 This commit allows to use 'typed' endpoints for the both Index and Get APIs relates compatible types-removal meta issue #54160
2021-03-23 17:59:21 +08:00
})
Consolidate REST API specifications and publish under Apache 2.0 license (#70036)
2021-03-27 07:20:14 +08:00
tasks.register('enforceYamlTestConvention').configure {
doLast {
if (fileTree('src/main/resources/rest-api-spec/test').files) {
throw new GradleException("There are YAML tests in src/main source set. These should be moved to src/yamlRestTest.")
}
}
}
tasks.named("precommit").configure {
dependsOn 'enforceYamlTestConvention'
}