From d730bba0916ec9a2f10631afaabfe70c110ce6d2 Mon Sep 17 00:00:00 2001 From: Isabelle Date: Sun, 18 Oct 2026 11:05:30 -0700 Subject: [PATCH] doc updates --- sdk/storage/azure-storage-blob/CHANGELOG.md | 6 ++++ .../blob/BlobContainerAsyncClient.java | 28 ++++++++++++++++ .../storage/blob/BlobContainerClient.java | 28 ++++++++++++++++ .../storage/blob/BlobServiceAsyncClient.java | 30 +++++++++++++++++ .../azure/storage/blob/BlobServiceClient.java | 28 ++++++++++++++++ .../azure-storage-file-datalake/CHANGELOG.md | 5 +++ .../DataLakeFileSystemAsyncClient.java | 32 +++++++++++++++++++ .../datalake/DataLakeFileSystemClient.java | 32 +++++++++++++++++++ .../datalake/DataLakeServiceAsyncClient.java | 17 ++++++++++ .../file/datalake/DataLakeServiceClient.java | 16 ++++++++++ 10 files changed, 222 insertions(+) diff --git a/sdk/storage/azure-storage-blob/CHANGELOG.md b/sdk/storage/azure-storage-blob/CHANGELOG.md index b1a5a3c2c34db..799a5b9af8d49 100644 --- a/sdk/storage/azure-storage-blob/CHANGELOG.md +++ b/sdk/storage/azure-storage-blob/CHANGELOG.md @@ -14,6 +14,12 @@ ### Other Changes +- Updated the documentation of `BlobContainerClient`/`BlobContainerAsyncClient` `delete`, `deleteWithResponse`, + `deleteIfExists`, and `deleteIfExistsWithResponse`, and `BlobServiceClient`/`BlobServiceAsyncClient` + `deleteBlobContainer`, `deleteBlobContainerWithResponse`, `deleteBlobContainerIfExists`, and + `deleteBlobContainerIfExistsWithResponse` to note that operations on blobs within a deleted container, including reads + and writes, may continue to succeed for up to 30 seconds after the delete request is accepted. + ## 12.35.2 (2026-10-06) ### Other Changes diff --git a/sdk/storage/azure-storage-blob/src/main/java/com/azure/storage/blob/BlobContainerAsyncClient.java b/sdk/storage/azure-storage-blob/src/main/java/com/azure/storage/blob/BlobContainerAsyncClient.java index 6f3a12dd90a5a..0eb333a0bb0f8 100644 --- a/sdk/storage/azure-storage-blob/src/main/java/com/azure/storage/blob/BlobContainerAsyncClient.java +++ b/sdk/storage/azure-storage-blob/src/main/java/com/azure/storage/blob/BlobContainerAsyncClient.java @@ -514,6 +514,13 @@ Mono> createIfNotExistsWithResponse(BlobContainerCreateOptions * during garbage collection. For more information, see the * Azure Docs. * + *

When a container is deleted, a container with the same name can't be created for at least 30 seconds. The + * container might not be available for more than 30 seconds if the service is still processing the request. While + * the container is being deleted, attempts to create a container of the same name fail with status code 409 + * (Conflict). The service indicates that the container is being deleted. Operations on blobs within the container, + * including reads and writes, may continue to succeed for up to 30 seconds after the delete request is accepted. + * After this period, all operations on the container and its blobs fail with status code 404 (Not Found).

+ * *

Code Samples

* * @@ -536,6 +543,13 @@ public Mono delete() { * during garbage collection. For more information, see the * Azure Docs. * + *

When a container is deleted, a container with the same name can't be created for at least 30 seconds. The + * container might not be available for more than 30 seconds if the service is still processing the request. While + * the container is being deleted, attempts to create a container of the same name fail with status code 409 + * (Conflict). The service indicates that the container is being deleted. Operations on blobs within the container, + * including reads and writes, may continue to succeed for up to 30 seconds after the delete request is accepted. + * After this period, all operations on the container and its blobs fail with status code 404 (Not Found).

+ * *

Code Samples

* * @@ -584,6 +598,13 @@ Mono> deleteWithResponse(BlobRequestConditions requestConditions, * during garbage collection. For more information, see the * Azure Docs. * + *

When a container is deleted, a container with the same name can't be created for at least 30 seconds. The + * container might not be available for more than 30 seconds if the service is still processing the request. While + * the container is being deleted, attempts to create a container of the same name fail with status code 409 + * (Conflict). The service indicates that the container is being deleted. Operations on blobs within the container, + * including reads and writes, may continue to succeed for up to 30 seconds after the delete request is accepted. + * After this period, all operations on the container and its blobs fail with status code 404 (Not Found).

+ * *

Code Samples

* * @@ -611,6 +632,13 @@ public Mono deleteIfExists() { * later deleted during garbage collection. For more information, see the * Azure Docs. * + *

When a container is deleted, a container with the same name can't be created for at least 30 seconds. The + * container might not be available for more than 30 seconds if the service is still processing the request. While + * the container is being deleted, attempts to create a container of the same name fail with status code 409 + * (Conflict). The service indicates that the container is being deleted. Operations on blobs within the container, + * including reads and writes, may continue to succeed for up to 30 seconds after the delete request is accepted. + * After this period, all operations on the container and its blobs fail with status code 404 (Not Found).

+ * *

Code Samples

* * diff --git a/sdk/storage/azure-storage-blob/src/main/java/com/azure/storage/blob/BlobContainerClient.java b/sdk/storage/azure-storage-blob/src/main/java/com/azure/storage/blob/BlobContainerClient.java index 67dc02480be42..1d8af9f3f2e14 100644 --- a/sdk/storage/azure-storage-blob/src/main/java/com/azure/storage/blob/BlobContainerClient.java +++ b/sdk/storage/azure-storage-blob/src/main/java/com/azure/storage/blob/BlobContainerClient.java @@ -497,6 +497,13 @@ public Response createIfNotExistsWithResponse(BlobContainerCreateOption * during garbage collection. For more information, see the * Azure Docs. * + *

When a container is deleted, a container with the same name can't be created for at least 30 seconds. The + * container might not be available for more than 30 seconds if the service is still processing the request. While + * the container is being deleted, attempts to create a container of the same name fail with status code 409 + * (Conflict). The service indicates that the container is being deleted. Operations on blobs within the container, + * including reads and writes, may continue to succeed for up to 30 seconds after the delete request is accepted. + * After this period, all operations on the container and its blobs fail with status code 404 (Not Found).

+ * *

Code Samples

* * @@ -522,6 +529,13 @@ public void delete() { * during garbage collection. For more information, see the * Azure Docs. * + *

When a container is deleted, a container with the same name can't be created for at least 30 seconds. The + * container might not be available for more than 30 seconds if the service is still processing the request. While + * the container is being deleted, attempts to create a container of the same name fail with status code 409 + * (Conflict). The service indicates that the container is being deleted. Operations on blobs within the container, + * including reads and writes, may continue to succeed for up to 30 seconds after the delete request is accepted. + * After this period, all operations on the container and its blobs fail with status code 404 (Not Found).

+ * *

Code Samples

* * @@ -565,6 +579,13 @@ public Response deleteWithResponse(BlobRequestConditions requestConditions * it are later deleted during garbage collection. For more information, see the * Azure Docs. * + *

When a container is deleted, a container with the same name can't be created for at least 30 seconds. The + * container might not be available for more than 30 seconds if the service is still processing the request. While + * the container is being deleted, attempts to create a container of the same name fail with status code 409 + * (Conflict). The service indicates that the container is being deleted. Operations on blobs within the container, + * including reads and writes, may continue to succeed for up to 30 seconds after the delete request is accepted. + * After this period, all operations on the container and its blobs fail with status code 404 (Not Found).

+ * *

Code Samples

* * @@ -585,6 +606,13 @@ public boolean deleteIfExists() { * are later deleted during garbage collection. For more information, see the * Azure Docs. * + *

When a container is deleted, a container with the same name can't be created for at least 30 seconds. The + * container might not be available for more than 30 seconds if the service is still processing the request. While + * the container is being deleted, attempts to create a container of the same name fail with status code 409 + * (Conflict). The service indicates that the container is being deleted. Operations on blobs within the container, + * including reads and writes, may continue to succeed for up to 30 seconds after the delete request is accepted. + * After this period, all operations on the container and its blobs fail with status code 404 (Not Found).

+ * *

Code Samples

* * diff --git a/sdk/storage/azure-storage-blob/src/main/java/com/azure/storage/blob/BlobServiceAsyncClient.java b/sdk/storage/azure-storage-blob/src/main/java/com/azure/storage/blob/BlobServiceAsyncClient.java index 3254b5da630db..67b8067fa30a7 100644 --- a/sdk/storage/azure-storage-blob/src/main/java/com/azure/storage/blob/BlobServiceAsyncClient.java +++ b/sdk/storage/azure-storage-blob/src/main/java/com/azure/storage/blob/BlobServiceAsyncClient.java @@ -337,6 +337,14 @@ Mono> createBlobContainerIfNotExistsWithRespo /** * Deletes the specified container in the storage account. If the container doesn't exist the operation fails. For * more information see the Azure Docs. + * + *

When a container is deleted, a container with the same name can't be created for at least 30 seconds. The + * container might not be available for more than 30 seconds if the service is still processing the request. While + * the container is being deleted, attempts to create a container of the same name fail with status code 409 + * (Conflict). The service indicates that the container is being deleted. Operations on blobs within the container, + * including reads and writes, may continue to succeed for up to 30 seconds after the delete request is accepted. + * After this period, all operations on the container and its blobs fail with status code 404 (Not Found).

+ * *

Code Samples

* * @@ -360,6 +368,13 @@ public Mono deleteBlobContainer(String containerName) { * more information see the Azure * Docs. * + *

When a container is deleted, a container with the same name can't be created for at least 30 seconds. The + * container might not be available for more than 30 seconds if the service is still processing the request. While + * the container is being deleted, attempts to create a container of the same name fail with status code 409 + * (Conflict). The service indicates that the container is being deleted. Operations on blobs within the container, + * including reads and writes, may continue to succeed for up to 30 seconds after the delete request is accepted. + * After this period, all operations on the container and its blobs fail with status code 404 (Not Found).

+ * *

Code Samples

* * @@ -391,6 +406,14 @@ Mono> deleteBlobContainerWithResponse(String containerName, Conte * Deletes the specified container in the storage account if it exists. For * more information see the Azure * Docs. + * + *

When a container is deleted, a container with the same name can't be created for at least 30 seconds. The + * container might not be available for more than 30 seconds if the service is still processing the request. While + * the container is being deleted, attempts to create a container of the same name fail with status code 409 + * (Conflict). The service indicates that the container is being deleted. Operations on blobs within the container, + * including reads and writes, may continue to succeed for up to 30 seconds after the delete request is accepted. + * After this period, all operations on the container and its blobs fail with status code 404 (Not Found).

+ * *

Code Samples

* * @@ -419,6 +442,13 @@ public Mono deleteBlobContainerIfExists(String containerName) { * For more information see the Azure * Docs. * + *

When a container is deleted, a container with the same name can't be created for at least 30 seconds. The + * container might not be available for more than 30 seconds if the service is still processing the request. While + * the container is being deleted, attempts to create a container of the same name fail with status code 409 + * (Conflict). The service indicates that the container is being deleted. Operations on blobs within the container, + * including reads and writes, may continue to succeed for up to 30 seconds after the delete request is accepted. + * After this period, all operations on the container and its blobs fail with status code 404 (Not Found).

+ * *

Code Samples

* * diff --git a/sdk/storage/azure-storage-blob/src/main/java/com/azure/storage/blob/BlobServiceClient.java b/sdk/storage/azure-storage-blob/src/main/java/com/azure/storage/blob/BlobServiceClient.java index 3ad51c9a9b5f9..364e2c9aae614 100644 --- a/sdk/storage/azure-storage-blob/src/main/java/com/azure/storage/blob/BlobServiceClient.java +++ b/sdk/storage/azure-storage-blob/src/main/java/com/azure/storage/blob/BlobServiceClient.java @@ -289,6 +289,13 @@ public Response createBlobContainerIfNotExistsWithResponse( * more information see the Azure * Docs. * + *

When a container is deleted, a container with the same name can't be created for at least 30 seconds. The + * container might not be available for more than 30 seconds if the service is still processing the request. While + * the container is being deleted, attempts to create a container of the same name fail with status code 409 + * (Conflict). The service indicates that the container is being deleted. Operations on blobs within the container, + * including reads and writes, may continue to succeed for up to 30 seconds after the delete request is accepted. + * After this period, all operations on the container and its blobs fail with status code 404 (Not Found).

+ * *

Code Samples

* * @@ -314,6 +321,13 @@ public void deleteBlobContainer(String containerName) { * more information see the Azure * Docs. * + *

When a container is deleted, a container with the same name can't be created for at least 30 seconds. The + * container might not be available for more than 30 seconds if the service is still processing the request. While + * the container is being deleted, attempts to create a container of the same name fail with status code 409 + * (Conflict). The service indicates that the container is being deleted. Operations on blobs within the container, + * including reads and writes, may continue to succeed for up to 30 seconds after the delete request is accepted. + * After this period, all operations on the container and its blobs fail with status code 404 (Not Found).

+ * * @param containerName Name of the container to delete * @param context Additional context that is passed through the Http pipeline during the service call. * @return A response containing status code and HTTP headers @@ -328,6 +342,13 @@ public Response deleteBlobContainerWithResponse(String containerName, Cont * more information see the Azure * Docs. * + *

When a container is deleted, a container with the same name can't be created for at least 30 seconds. The + * container might not be available for more than 30 seconds if the service is still processing the request. While + * the container is being deleted, attempts to create a container of the same name fail with status code 409 + * (Conflict). The service indicates that the container is being deleted. Operations on blobs within the container, + * including reads and writes, may continue to succeed for up to 30 seconds after the delete request is accepted. + * After this period, all operations on the container and its blobs fail with status code 404 (Not Found).

+ * *

Code Samples

* * @@ -350,6 +371,13 @@ public boolean deleteBlobContainerIfExists(String containerName) { * more information see the Azure * Docs. * + *

When a container is deleted, a container with the same name can't be created for at least 30 seconds. The + * container might not be available for more than 30 seconds if the service is still processing the request. While + * the container is being deleted, attempts to create a container of the same name fail with status code 409 + * (Conflict). The service indicates that the container is being deleted. Operations on blobs within the container, + * including reads and writes, may continue to succeed for up to 30 seconds after the delete request is accepted. + * After this period, all operations on the container and its blobs fail with status code 404 (Not Found).

+ * *

Code Samples

* * diff --git a/sdk/storage/azure-storage-file-datalake/CHANGELOG.md b/sdk/storage/azure-storage-file-datalake/CHANGELOG.md index 07c08f8257fd1..ea12450e3b0e5 100644 --- a/sdk/storage/azure-storage-file-datalake/CHANGELOG.md +++ b/sdk/storage/azure-storage-file-datalake/CHANGELOG.md @@ -19,6 +19,11 @@ - Corrected documentation on `DataLakeFileSystemClient`/`DataLakeFileSystemAsyncClient` path client getters and on `DataLakePathClientBuilder.pathName(String)`, which incorrectly instructed callers to pass a URL-encoded path name. Path names have been used verbatim since 12.22.0 and are percent-encoded by the client when the request URL is built. +- Updated the documentation of `DataLakeFileSystemClient`/`DataLakeFileSystemAsyncClient` `delete`, + `deleteWithResponse`, `deleteIfExists`, and `deleteIfExistsWithResponse`, and + `DataLakeServiceClient`/`DataLakeServiceAsyncClient` `deleteFileSystem` and `deleteFileSystemWithResponse` to note + that operations on paths within a deleted file system, including reads and writes, may continue to succeed for up to + 30 seconds after the delete request is accepted. ## 12.28.2 (2026-10-06) diff --git a/sdk/storage/azure-storage-file-datalake/src/main/java/com/azure/storage/file/datalake/DataLakeFileSystemAsyncClient.java b/sdk/storage/azure-storage-file-datalake/src/main/java/com/azure/storage/file/datalake/DataLakeFileSystemAsyncClient.java index ab7ba75549d5f..3d1c0b79810c4 100644 --- a/sdk/storage/azure-storage-file-datalake/src/main/java/com/azure/storage/file/datalake/DataLakeFileSystemAsyncClient.java +++ b/sdk/storage/azure-storage-file-datalake/src/main/java/com/azure/storage/file/datalake/DataLakeFileSystemAsyncClient.java @@ -424,6 +424,14 @@ public Mono> createIfNotExistsWithResponse(Map * later deleted during garbage collection. For more information, see the * Azure Docs. * + *

When a file system is deleted, a file system with the same name can't be created for at least 30 seconds. The + * file system might not be available for more than 30 seconds if the service is still processing the request. While + * the file system is being deleted, attempts to create a file system of the same name fail with status code 409 + * (Conflict). The service indicates that the file system is being deleted. Operations on paths within the file + * system, including reads and writes, may continue to succeed for up to 30 seconds after the delete request is + * accepted. After this period, all operations on the file system and its paths fail with status code 404 (Not + * Found).

+ * *

Code Samples

* * @@ -446,6 +454,14 @@ public Mono delete() { * later deleted during garbage collection. For more information, see the * Azure Docs. * + *

When a file system is deleted, a file system with the same name can't be created for at least 30 seconds. The + * file system might not be available for more than 30 seconds if the service is still processing the request. While + * the file system is being deleted, attempts to create a file system of the same name fail with status code 409 + * (Conflict). The service indicates that the file system is being deleted. Operations on paths within the file + * system, including reads and writes, may continue to succeed for up to 30 seconds after the delete request is + * accepted. After this period, all operations on the file system and its paths fail with status code 404 (Not + * Found).

+ * *

Code Samples

* * @@ -475,6 +491,14 @@ public Mono> deleteWithResponse(DataLakeRequestConditions request * later deleted during garbage collection. For more information, see the * Azure Docs. * + *

When a file system is deleted, a file system with the same name can't be created for at least 30 seconds. The + * file system might not be available for more than 30 seconds if the service is still processing the request. While + * the file system is being deleted, attempts to create a file system of the same name fail with status code 409 + * (Conflict). The service indicates that the file system is being deleted. Operations on paths within the file + * system, including reads and writes, may continue to succeed for up to 30 seconds after the delete request is + * accepted. After this period, all operations on the file system and its paths fail with status code 404 (Not + * Found).

+ * *

Code Samples

* * @@ -502,6 +526,14 @@ public Mono deleteIfExists() { * later deleted during garbage collection. For more information, see the * Azure Docs. * + *

When a file system is deleted, a file system with the same name can't be created for at least 30 seconds. The + * file system might not be available for more than 30 seconds if the service is still processing the request. While + * the file system is being deleted, attempts to create a file system of the same name fail with status code 409 + * (Conflict). The service indicates that the file system is being deleted. Operations on paths within the file + * system, including reads and writes, may continue to succeed for up to 30 seconds after the delete request is + * accepted. After this period, all operations on the file system and its paths fail with status code 404 (Not + * Found).

+ * *

Code Samples

* * diff --git a/sdk/storage/azure-storage-file-datalake/src/main/java/com/azure/storage/file/datalake/DataLakeFileSystemClient.java b/sdk/storage/azure-storage-file-datalake/src/main/java/com/azure/storage/file/datalake/DataLakeFileSystemClient.java index 9e97dc2dffd34..f897f34aeba35 100644 --- a/sdk/storage/azure-storage-file-datalake/src/main/java/com/azure/storage/file/datalake/DataLakeFileSystemClient.java +++ b/sdk/storage/azure-storage-file-datalake/src/main/java/com/azure/storage/file/datalake/DataLakeFileSystemClient.java @@ -399,6 +399,14 @@ public Response createIfNotExistsWithResponse(Map metad * later deleted during garbage collection. For more information, see the * Azure Docs. * + *

When a file system is deleted, a file system with the same name can't be created for at least 30 seconds. The + * file system might not be available for more than 30 seconds if the service is still processing the request. While + * the file system is being deleted, attempts to create a file system of the same name fail with status code 409 + * (Conflict). The service indicates that the file system is being deleted. Operations on paths within the file + * system, including reads and writes, may continue to succeed for up to 30 seconds after the delete request is + * accepted. After this period, all operations on the file system and its paths fail with status code 404 (Not + * Found).

+ * *

Code Samples

* * @@ -424,6 +432,14 @@ public void delete() { * later deleted during garbage collection. For more information, see the * Azure Docs. * + *

When a file system is deleted, a file system with the same name can't be created for at least 30 seconds. The + * file system might not be available for more than 30 seconds if the service is still processing the request. While + * the file system is being deleted, attempts to create a file system of the same name fail with status code 409 + * (Conflict). The service indicates that the file system is being deleted. Operations on paths within the file + * system, including reads and writes, may continue to succeed for up to 30 seconds after the delete request is + * accepted. After this period, all operations on the file system and its paths fail with status code 404 (Not + * Found).

+ * *

Code Samples

* * @@ -455,6 +471,14 @@ public Response deleteWithResponse(DataLakeRequestConditions requestCondit * later deleted during garbage collection. For more information, see the * Azure Docs. * + *

When a file system is deleted, a file system with the same name can't be created for at least 30 seconds. The + * file system might not be available for more than 30 seconds if the service is still processing the request. While + * the file system is being deleted, attempts to create a file system of the same name fail with status code 409 + * (Conflict). The service indicates that the file system is being deleted. Operations on paths within the file + * system, including reads and writes, may continue to succeed for up to 30 seconds after the delete request is + * accepted. After this period, all operations on the file system and its paths fail with status code 404 (Not + * Found).

+ * *

Code Samples

* * @@ -474,6 +498,14 @@ public boolean deleteIfExists() { * later deleted during garbage collection. For more information, see the * Azure Docs. * + *

When a file system is deleted, a file system with the same name can't be created for at least 30 seconds. The + * file system might not be available for more than 30 seconds if the service is still processing the request. While + * the file system is being deleted, attempts to create a file system of the same name fail with status code 409 + * (Conflict). The service indicates that the file system is being deleted. Operations on paths within the file + * system, including reads and writes, may continue to succeed for up to 30 seconds after the delete request is + * accepted. After this period, all operations on the file system and its paths fail with status code 404 (Not + * Found).

+ * *

Code Samples

* * diff --git a/sdk/storage/azure-storage-file-datalake/src/main/java/com/azure/storage/file/datalake/DataLakeServiceAsyncClient.java b/sdk/storage/azure-storage-file-datalake/src/main/java/com/azure/storage/file/datalake/DataLakeServiceAsyncClient.java index 7e509ea67bbee..227d99c5f80d1 100644 --- a/sdk/storage/azure-storage-file-datalake/src/main/java/com/azure/storage/file/datalake/DataLakeServiceAsyncClient.java +++ b/sdk/storage/azure-storage-file-datalake/src/main/java/com/azure/storage/file/datalake/DataLakeServiceAsyncClient.java @@ -204,6 +204,15 @@ public Mono> createFileSystemWithRespons * Deletes the specified file system in the storage account. If the file system doesn't exist the operation fails. * For more information see the Azure * Docs. + * + *

When a file system is deleted, a file system with the same name can't be created for at least 30 seconds. The + * file system might not be available for more than 30 seconds if the service is still processing the request. While + * the file system is being deleted, attempts to create a file system of the same name fail with status code 409 + * (Conflict). The service indicates that the file system is being deleted. Operations on paths within the file + * system, including reads and writes, may continue to succeed for up to 30 seconds after the delete request is + * accepted. After this period, all operations on the file system and its paths fail with status code 404 (Not + * Found).

+ * *

Code Samples

* * @@ -227,6 +236,14 @@ public Mono deleteFileSystem(String fileSystemName) { * For more information see the Azure * Docs. * + *

When a file system is deleted, a file system with the same name can't be created for at least 30 seconds. The + * file system might not be available for more than 30 seconds if the service is still processing the request. While + * the file system is being deleted, attempts to create a file system of the same name fail with status code 409 + * (Conflict). The service indicates that the file system is being deleted. Operations on paths within the file + * system, including reads and writes, may continue to succeed for up to 30 seconds after the delete request is + * accepted. After this period, all operations on the file system and its paths fail with status code 404 (Not + * Found).

+ * *

Code Samples

* * diff --git a/sdk/storage/azure-storage-file-datalake/src/main/java/com/azure/storage/file/datalake/DataLakeServiceClient.java b/sdk/storage/azure-storage-file-datalake/src/main/java/com/azure/storage/file/datalake/DataLakeServiceClient.java index 5dab7e976d36d..0724bcab0cc5d 100644 --- a/sdk/storage/azure-storage-file-datalake/src/main/java/com/azure/storage/file/datalake/DataLakeServiceClient.java +++ b/sdk/storage/azure-storage-file-datalake/src/main/java/com/azure/storage/file/datalake/DataLakeServiceClient.java @@ -183,6 +183,14 @@ public Response createFileSystemWithResponse(String fi * For more information see the Azure * Docs. * + *

When a file system is deleted, a file system with the same name can't be created for at least 30 seconds. The + * file system might not be available for more than 30 seconds if the service is still processing the request. While + * the file system is being deleted, attempts to create a file system of the same name fail with status code 409 + * (Conflict). The service indicates that the file system is being deleted. Operations on paths within the file + * system, including reads and writes, may continue to succeed for up to 30 seconds after the delete request is + * accepted. After this period, all operations on the file system and its paths fail with status code 404 (Not + * Found).

+ * *

Code Samples

* * @@ -208,6 +216,14 @@ public void deleteFileSystem(String fileSystemName) { * For more information see the Azure * Docs. * + *

When a file system is deleted, a file system with the same name can't be created for at least 30 seconds. The + * file system might not be available for more than 30 seconds if the service is still processing the request. While + * the file system is being deleted, attempts to create a file system of the same name fail with status code 409 + * (Conflict). The service indicates that the file system is being deleted. Operations on paths within the file + * system, including reads and writes, may continue to succeed for up to 30 seconds after the delete request is + * accepted. After this period, all operations on the file system and its paths fail with status code 404 (Not + * Found).

+ * *

Code Samples

* *