OpenSearch/plugins/cloud-azure/pom.xml

77 lines
3.1 KiB
XML
Raw Normal View History

<?xml version="1.0" encoding="UTF-8"?>
<!-- Licensed to Elasticsearch under one or more contributor
license agreements. See the NOTICE file distributed with this work for additional
information regarding copyright ownership. ElasticSearch licenses this file to you
under the Apache License, Version 2.0 (the "License"); you may not use this
file except in compliance with the License. You may obtain a copy of the
License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by
applicable law or agreed to in writing, software distributed under the License
is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the specific language
governing permissions and limitations under the License. -->
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
2015-03-28 06:36:26 -04:00
<parent>
[maven] change groupId / artifactId When we generate our project, we can get something like: ``` ├── dev-tools ├── elasticsearch ├── elasticsearch-parent ├── elasticsearch-plugin ├── plugin │   ├── elasticsearch-analysis-icu │   ├── elasticsearch-analysis-kuromoji │   ├── elasticsearch-analysis-phonetic │   ├── elasticsearch-analysis-smartcn │   ├── elasticsearch-analysis-stempel │   ├── elasticsearch-cloud-aws │   ├── elasticsearch-cloud-azure │   ├── elasticsearch-cloud-gce │   ├── elasticsearch-delete-by-query │   ├── elasticsearch-lang-javascript │   └── elasticsearch-lang-python ├── rest-api-spec └── securemock ``` I propose here to use a common naming for artifacts: start always with `elasticsearch-`. Also, move `elasticsearch-plugin` to `org.elasticsearch.plugin` groupId. So we could have: ``` ├── elasticsearch ├── elasticsearch-dev-tools ├── elasticsearch-parent ├── elasticsearch-rest-api-spec ├── elasticsearch-securemock ├── plugin │   ├── elasticsearch-analysis-icu │   ├── elasticsearch-analysis-kuromoji │   ├── elasticsearch-analysis-phonetic │   ├── elasticsearch-analysis-smartcn │   ├── elasticsearch-analysis-stempel │   ├── elasticsearch-cloud-aws │   ├── elasticsearch-cloud-azure │   ├── elasticsearch-cloud-gce │   ├── elasticsearch-delete-by-query │   ├── elasticsearch-lang-javascript │   ├── elasticsearch-lang-python │   └── elasticsearch-plugin ```
2015-07-03 14:00:32 -04:00
<groupId>org.elasticsearch.plugin</groupId>
2015-05-21 22:52:44 -04:00
<artifactId>elasticsearch-plugin</artifactId>
2015-03-28 06:36:26 -04:00
<version>2.0.0-SNAPSHOT</version>
</parent>
[maven] change groupId / artifactId When we generate our project, we can get something like: ``` ├── dev-tools ├── elasticsearch ├── elasticsearch-parent ├── elasticsearch-plugin ├── plugin │   ├── elasticsearch-analysis-icu │   ├── elasticsearch-analysis-kuromoji │   ├── elasticsearch-analysis-phonetic │   ├── elasticsearch-analysis-smartcn │   ├── elasticsearch-analysis-stempel │   ├── elasticsearch-cloud-aws │   ├── elasticsearch-cloud-azure │   ├── elasticsearch-cloud-gce │   ├── elasticsearch-delete-by-query │   ├── elasticsearch-lang-javascript │   └── elasticsearch-lang-python ├── rest-api-spec └── securemock ``` I propose here to use a common naming for artifacts: start always with `elasticsearch-`. Also, move `elasticsearch-plugin` to `org.elasticsearch.plugin` groupId. So we could have: ``` ├── elasticsearch ├── elasticsearch-dev-tools ├── elasticsearch-parent ├── elasticsearch-rest-api-spec ├── elasticsearch-securemock ├── plugin │   ├── elasticsearch-analysis-icu │   ├── elasticsearch-analysis-kuromoji │   ├── elasticsearch-analysis-phonetic │   ├── elasticsearch-analysis-smartcn │   ├── elasticsearch-analysis-stempel │   ├── elasticsearch-cloud-aws │   ├── elasticsearch-cloud-azure │   ├── elasticsearch-cloud-gce │   ├── elasticsearch-delete-by-query │   ├── elasticsearch-lang-javascript │   ├── elasticsearch-lang-python │   └── elasticsearch-plugin ```
2015-07-03 14:00:32 -04:00
<artifactId>elasticsearch-cloud-azure</artifactId>
<name>Elasticsearch Azure cloud plugin</name>
<description>The Azure Cloud plugin allows to use Azure API for the unicast discovery mechanism and add Azure storage repositories.</description>
<properties>
<!-- You can add any specific project property here -->
<tests.jvms>1</tests.jvms>
2015-07-07 13:03:37 -04:00
<tests.rest.suite>cloud_azure</tests.rest.suite>
<tests.rest.load_packaged>false</tests.rest.load_packaged>
</properties>
<dependencies>
<!-- Azure API -->
Add Azure Storage repository elasticsearch 1.0 will provide a new feature named `Snapshot & Restore`. We want to add support for [Azure Storage](http://www.windowsazure.com/en-us/documentation/services/storage/). To enable Azure repositories, you have first to set your azure storage settings: ```yaml cloud: azure: storage_account: your_azure_storage_account storage_key: your_azure_storage_key ``` The Azure repository supports following settings: * `container`: Container name. Defaults to `elasticsearch-snapshots` * `base_path`: Specifies the path within container to repository data. Defaults to empty (root directory). * `concurrent_streams`: Throttles the number of streams (per node) preforming snapshot operation. Defaults to `5`. * `chunk_size`: Big files can be broken down into chunks during snapshotting if needed. The chunk size can be specified in bytes or by using size value notation, i.e. `1g`, `10m`, `5k`. Defaults to `64m` (64m max) * `compress`: When set to `true` metadata files are stored in compressed format. This setting doesn't affect index files that are already compressed by default. Defaults to `false`. Some examples, using scripts: ```sh $ curl -XPUT 'http://localhost:9200/_snapshot/my_backup1' -d '{ "type": "azure" }' $ curl -XPUT 'http://localhost:9200/_snapshot/my_backup2' -d '{ "type": "azure", "settings": { "container": "backup_container", "base_path": "backups", "concurrent_streams": 2, "chunk_size": "32m", "compress": true } }' ``` Example using Java: ```java client.admin().cluster().preparePutRepository("my_backup3") .setType("azure").setSettings(ImmutableSettings.settingsBuilder() .put(AzureStorageService.Fields.CONTAINER, "backup_container") .put(AzureStorageService.Fields.CHUNK_SIZE, new ByteSizeValue(32, ByteSizeUnit.MB)) ).get(); ``` Closes #2.
2014-01-06 17:14:34 -05:00
<dependency>
<groupId>com.microsoft.azure</groupId>
<artifactId>azure-storage</artifactId>
<version>2.0.0</version>
Add Azure Storage repository elasticsearch 1.0 will provide a new feature named `Snapshot & Restore`. We want to add support for [Azure Storage](http://www.windowsazure.com/en-us/documentation/services/storage/). To enable Azure repositories, you have first to set your azure storage settings: ```yaml cloud: azure: storage_account: your_azure_storage_account storage_key: your_azure_storage_key ``` The Azure repository supports following settings: * `container`: Container name. Defaults to `elasticsearch-snapshots` * `base_path`: Specifies the path within container to repository data. Defaults to empty (root directory). * `concurrent_streams`: Throttles the number of streams (per node) preforming snapshot operation. Defaults to `5`. * `chunk_size`: Big files can be broken down into chunks during snapshotting if needed. The chunk size can be specified in bytes or by using size value notation, i.e. `1g`, `10m`, `5k`. Defaults to `64m` (64m max) * `compress`: When set to `true` metadata files are stored in compressed format. This setting doesn't affect index files that are already compressed by default. Defaults to `false`. Some examples, using scripts: ```sh $ curl -XPUT 'http://localhost:9200/_snapshot/my_backup1' -d '{ "type": "azure" }' $ curl -XPUT 'http://localhost:9200/_snapshot/my_backup2' -d '{ "type": "azure", "settings": { "container": "backup_container", "base_path": "backups", "concurrent_streams": 2, "chunk_size": "32m", "compress": true } }' ``` Example using Java: ```java client.admin().cluster().preparePutRepository("my_backup3") .setType("azure").setSettings(ImmutableSettings.settingsBuilder() .put(AzureStorageService.Fields.CONTAINER, "backup_container") .put(AzureStorageService.Fields.CHUNK_SIZE, new ByteSizeValue(32, ByteSizeUnit.MB)) ).get(); ``` Closes #2.
2014-01-06 17:14:34 -05:00
</dependency>
<dependency>
<groupId>com.microsoft.azure</groupId>
<artifactId>azure-management-compute</artifactId>
<version>0.7.0</version>
<exclusions>
<exclusion>
<groupId>stax</groupId>
<artifactId>stax-api</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>com.microsoft.azure</groupId>
<artifactId>azure-management</artifactId>
<version>0.7.0</version>
</dependency>
<!-- We need to force here the compile scope as it was defined as test scope in plugins/pom.xml -->
<!-- TODO: remove this dependency when we will have a REST Test module -->
<dependency>
<groupId>org.apache.httpcomponents</groupId>
<artifactId>httpclient</artifactId>
<scope>compile</scope>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
</plugin>
</plugins>
</build>
</project>