root
/
elasticsearch
mirror of https://github.com/elastic/elasticsearch.git
1
0
Fork 0
Code Issues Actions 1 Packages Projects Releases Wiki Activity
elasticsearch/x-pack/plugin/spatial/build.gradle

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

34 lines
956 B
Groovy
Raw Normal View History

Remove internal build logic from public build tool plugins (#72470) Extract usage of internal API from TestClustersPlugin and PluginBuildPlugin and related plugins and build logic This includes a refactoring of ElasticsearchDistribution to handle types better in a way we can differentiate between supported Elasticsearch Distribution types supported in TestCkustersPlugin and types only supported in internal plugins. It also introduces a set of internal versions of public plugins. As part of this we also generate the plugin descriptors now. As a follow up on this we can actually move these public used classes into an extra project (declared as included build) We keep LoggedExec and VersionProperties effectively public And workaround for RestTestBase
2021-05-06 20:02:35 +08:00
apply plugin: 'elasticsearch.internal-es-plugin'
Convert second 1/2 x-pack plugins from integTest to [yaml | java]RestTest or internalClusterTest (#61802) For 1/2 the plugins in x-pack, the integTest task is now a no-op and all of the tests are now executed via a test, yamlRestTest, javaRestTest, or internalClusterTest. This includes the following projects: security, spatial, stack, transform, vecotrs, voting-only-node, and watcher. A few of the more specialized qa projects within these plugins have not been changed with this PR due to additional complexity which should be addressed separately. related: #60630 related: #56841 related: #59939 related: #55896
2020-09-02 22:23:26 +08:00
apply plugin: 'elasticsearch.internal-cluster-test'
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 REST API compatibility testing for the :x-pack plugins (#71302)
2021-04-06 23:35:33 +08:00
apply plugin: 'elasticsearch.yaml-rest-compat-test'
Introduce Spatial Plugin (#44389) This commit introduces a skeleton Spatial plugin that will be filled-in with some new licensed features coming to Geo/Spatial land!
2019-07-18 05:18:31 +08:00
esplugin {
Apply 2-space indent to all gradle scripts (#48849) Closes #48724. Update `.editorconfig` to make the Java settings the default for all files, and then apply a 2-space indent to all `*.gradle` files. Then reformat all the files.
2019-11-13 18:14:04 +08:00
name 'spatial'
description 'A plugin for Basic Spatial features'
classname 'org.elasticsearch.xpack.spatial.SpatialPlugin'
extendedPlugins = ['x-pack-core']
Introduce Spatial Plugin (#44389) This commit introduces a skeleton Spatial plugin that will be filled-in with some new licensed features coming to Geo/Spatial land!
2019-07-18 05:18:31 +08:00
}
dependencies {
Remove deprecated usage of default configuration (#68575) This has been deprecated in gradle before but we havnt been warned. Gradle 7.0 will likely introduce a change in behaviour here that we should fix the usage of this configuration upfront. See https://github.com/gradle/gradle/issues/16027 for further information about the change in Gradle 7.0
2021-02-07 19:08:02 +08:00
compileOnly project(path: xpackModule('core'))
Introduce Internal Test Artifact Plugin (#68766) This reduces the ceremony declaring test artifacts for a project. It also solves an issue with usage of deprecated testRuntime that testArtifacts extendsFrom which seems not required at all and would have broke with Gradle 7.0 anyhow Test artifact resolution is now variant aware which allows us a more adequate compile and runtime classpath for the consuming projects. We also Introduce a convention method in the elasticsearch build to declare test artifact dependencies in an easy way close to how its done by the gradle build in test fixture plugin. Furthermore we cleaned up some inconsistent test dependencies declarations when relying on a project and on its test artifacts
2021-02-16 21:36:17 +08:00
testImplementation(testArtifact(project(xpackModule('core'))))
Add 'mvt' field type format to geo fields (#75367) In this commit we extend the Fields API formats for geo data in order to produce vector tiles features directly on the data nodes. That helps the vector tile API to reduce the size of the data that needs to pull in order to create the answer.
2021-07-28 15:24:54 +08:00
testImplementation project(path: xpackModule('vector-tile'))
Introduce Internal Test Artifact Plugin (#68766) This reduces the ceremony declaring test artifacts for a project. It also solves an issue with usage of deprecated testRuntime that testArtifacts extendsFrom which seems not required at all and would have broke with Gradle 7.0 anyhow Test artifact resolution is now variant aware which allows us a more adequate compile and runtime classpath for the consuming projects. We also Introduce a convention method in the elasticsearch build to declare test artifact dependencies in an easy way close to how its done by the gradle build in test fixture plugin. Furthermore we cleaned up some inconsistent test dependencies declarations when relying on a project and on its test artifacts
2021-02-16 21:36:17 +08:00
yamlRestTestImplementation(testArtifact(project(xpackModule('core'))))
Add geo_shape mapper supporting doc-values in Spatial Plugin (#55037) After #53562, the `geo_shape` field mapper is registered within a module. This opens the door for introducing a new `geo_shape` field mapper into the Spatial Plugin that has doc-values support. This is very much an extension of server's GeoShapeFieldMapper, but with the addition of the doc values implementation.
2020-04-17 00:18:09 +08:00
}
restResources {
restApi {
Consolidate REST API specifications and publish under Apache 2.0 license (#70036)
2021-03-27 07:20:14 +08:00
include '_common', 'bulk', 'indices', 'index', 'search', 'xpack'
Add geo_shape mapper supporting doc-values in Spatial Plugin (#55037) After #53562, the `geo_shape` field mapper is registered within a module. This opens the door for introducing a new `geo_shape` field mapper into the Spatial Plugin that has doc-values support. This is very much an extension of server's GeoShapeFieldMapper, but with the addition of the doc values implementation.
2020-04-17 00:18:09 +08:00
}
restTests {
includeCore 'geo_shape'
}
}
Convert second 1/2 x-pack plugins from integTest to [yaml | java]RestTest or internalClusterTest (#61802) For 1/2 the plugins in x-pack, the integTest task is now a no-op and all of the tests are now executed via a test, yamlRestTest, javaRestTest, or internalClusterTest. This includes the following projects: security, spatial, stack, transform, vecotrs, voting-only-node, and watcher. A few of the more specialized qa projects within these plugins have not been changed with this PR due to additional complexity which should be addressed separately. related: #60630 related: #56841 related: #59939 related: #55896
2020-09-02 22:23:26 +08:00
testClusters.all {
Add geo_shape support for the geo_centroid aggregation (#55602) this commit leverages the new geo_shape doc values to register a new geo_centroid aggregator that works on geo_shape field.
2020-04-28 00:03:05 +08:00
setting 'xpack.license.self_generated.type', 'trial'
Add geo_shape mapper supporting doc-values in Spatial Plugin (#55037) After #53562, the `geo_shape` field mapper is registered within a module. This opens the door for introducing a new `geo_shape` field mapper into the Spatial Plugin that has doc-values support. This is very much an extension of server's GeoShapeFieldMapper, but with the addition of the doc values implementation.
2020-04-17 00:18:09 +08:00
testDistribution = 'DEFAULT'
Warn users if security is implicitly disabled (#70114) * Warn users if security is implicitly disabled Elasticsearch has security features implicitly disabled by default for Basic and Trial licenses, unless explicitly set in the configuration file. This may be good for onboarding, but it also lead to unintended insecure clusters. This change introduces clear warnings when security features are implicitly disabled. - a warning header in each REST response if security is implicitly disabled; - a log message during cluster boot.
2021-04-14 00:33:41 +08:00
setting 'xpack.security.enabled', 'false'
initial skeleton of vector tiles prototype implementation (#69338)
2021-03-31 01:09:07 +08:00
}