Class AzureRepositorySettings
- All Implemented Interfaces:
JsonpSerializable
- See Also:
-
Nested Class Summary
Nested ClassesNested classes/interfaces inherited from class co.elastic.clients.elasticsearch.snapshot.RepositorySettingsBase
RepositorySettingsBase.AbstractBuilder<BuilderT extends RepositorySettingsBase.AbstractBuilder<BuilderT>>
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final JsonpDeserializer<AzureRepositorySettings>
Json deserializer forAzureRepositorySettings
-
Method Summary
Modifier and TypeMethodDescriptionfinal String
basePath()
The path to the repository data within the container.final String
client()
The name of the Azure repository client to use.final String
The Azure container.final Integer
The maxmimum batch size, between 1 and 256, used forBlobBatch
requests.final String
Eitherprimary_only
orsecondary_only
.final Integer
The maximum number of concurrent batch delete requests that will be submitted for any individual bulk delete withBlobBatch
.static AzureRepositorySettings
final Boolean
readonly()
Iftrue
, the repository is read-only.protected void
serializeInternal
(jakarta.json.stream.JsonGenerator generator, JsonpMapper mapper) protected static void
Methods inherited from class co.elastic.clients.elasticsearch.snapshot.RepositorySettingsBase
chunkSize, compress, maxRestoreBytesPerSec, maxSnapshotBytesPerSec, serialize, setupRepositorySettingsBaseDeserializer, toString
-
Field Details
-
_DESERIALIZER
Json deserializer forAzureRepositorySettings
-
-
Method Details
-
of
public static AzureRepositorySettings of(Function<AzureRepositorySettings.Builder, ObjectBuilder<AzureRepositorySettings>> fn) -
basePath
The path to the repository data within the container. It defaults to the root directory.NOTE: Don't set
base_path
when configuring a snapshot repository for Elastic Cloud Enterprise. Elastic Cloud Enterprise automatically generates thebase_path
for each deployment so that multiple deployments can share the same bucket.API name:
base_path
-
client
The name of the Azure repository client to use.API name:
client
-
container
The Azure container.API name:
container
-
deleteObjectsMaxSize
The maxmimum batch size, between 1 and 256, used forBlobBatch
requests. Defaults to 256 which is the maximum number supported by the Azure blob batch API.API name:
delete_objects_max_size
-
locationMode
Eitherprimary_only
orsecondary_only
. Note that if you set it tosecondary_only
, it will forcereadonly
totrue
.API name:
location_mode
-
maxConcurrentBatchDeletes
The maximum number of concurrent batch delete requests that will be submitted for any individual bulk delete withBlobBatch
. Note that the effective number of concurrent deletes is further limited by the Azure client connection and event loop thread limits. Defaults to 10, minimum is 1, maximum is 100.API name:
max_concurrent_batch_deletes
-
readonly
Iftrue
, the repository is read-only. The cluster can retrieve and restore snapshots from the repository but not write to the repository or create snapshots in it.Only a cluster with write access can create snapshots in the repository. All other clusters connected to the repository should have the
readonly
parameter set totrue
. Iffalse
, the cluster can write to the repository and create snapshots in it.IMPORTANT: If you register the same snapshot repository with multiple clusters, only one cluster should have write access to the repository. Having multiple clusters write to the repository at the same time risks corrupting the contents of the repository.
API name:
readonly
-
serializeInternal
- Overrides:
serializeInternal
in classRepositorySettingsBase
-
setupAzureRepositorySettingsDeserializer
protected static void setupAzureRepositorySettingsDeserializer(ObjectDeserializer<AzureRepositorySettings.Builder> op)
-