Azure Storage Blobs Batch client library for Java - Version 12.10.0
Azure Blob storage is Microsoft's object storage solution for the cloud. Blob storage is optimized for storing massive amounts of unstructured data. Unstructured data is data that does not adhere to a particular data model or definition, such as text or binary data.
Include the package
<dependency> <groupId>com.azure</groupId> <artifactId>azure-storage-blob-batch</artifactId> <version>12.10.0</version> </dependency>
Create a Storage Account
az storage account create \ --resource-group <resource-group-name> \ --name <storage-account-name> \ --location <location>
Blob storage is designed for:
- Serving images or documents directly to a browser.
- Storing files for distributed access.
- Streaming video and audio.
- Writing to log files.
- Storing data for backup and restore, disaster recovery, and archiving.
- Storing data for analysis by an on-premises or Azure-hosted service.
The following sections provide several code snippets covering some of the most common Azure Storage Blob Batch tasks, including:
Create a BlobBatchClient from a BlobServiceClient.
BlobBatchClient blobBatchClient = new BlobBatchClientBuilder(blobServiceClient).buildClient();
Bulk Deleting Blobs
blobBatchClient.deleteBlobs(blobUrls, DeleteSnapshotsOptionType.INCLUDE).forEach(response -> System.out.printf("Deleting blob with URL %s completed with status code %d%n", response.getRequest().getUrl(), response.getStatusCode()));
Bulk Setting AccessTier
blobBatchClient.setBlobsAccessTier(blobUrls, AccessTier.HOT).forEach(response -> System.out.printf("Setting blob access tier with URL %s completed with status code %d%n", response.getRequest().getUrl(), response.getStatusCode()));
Deleting blobs in a batch that have different pre-requisites.
BlobBatch blobBatch = blobBatchClient.getBlobBatch(); // Delete a blob. Response<Void> deleteResponse = blobBatch.deleteBlob(blobUrl); // Delete a specific blob snapshot. Response<Void> deleteSnapshotResponse = blobBatch.deleteBlob(blobUrlWithSnapshot, DeleteSnapshotsOptionType.ONLY, null); // Delete a blob that has a lease. Response<Void> deleteWithLeaseResponse = blobBatch.deleteBlob(blobUrlWithLease, DeleteSnapshotsOptionType.INCLUDE, new BlobRequestConditions() .setLeaseId("leaseId")); blobBatchClient.submitBatch(blobBatch); System.out.printf("Deleting blob completed with status code %d%n", deleteResponse.getStatusCode()); System.out.printf("Deleting blob snapshot completed with status code %d%n", deleteSnapshotResponse.getStatusCode()); System.out.printf("Deleting blob with lease completed with status code %d%n", deleteWithLeaseResponse.getStatusCode());
AccessTier on blobs in batch that have different pre-requisites.
BlobBatch blobBatch = blobBatchClient.getBlobBatch(); // Set AccessTier on a blob. Response<Void> setTierResponse = blobBatch.setBlobAccessTier(blobUrl, AccessTier.COOL); // Set AccessTier on another blob. Response<Void> setTierResponse2 = blobBatch.setBlobAccessTier(blobUrl2, AccessTier.ARCHIVE); // Set AccessTier on a blob that has a lease. Response<Void> setTierWithLeaseResponse = blobBatch.setBlobAccessTier(blobUrlWithLease, AccessTier.HOT, "leaseId"); blobBatchClient.submitBatch(blobBatch); System.out.printf("Set AccessTier on blob completed with status code %d%n", setTierResponse.getStatusCode()); System.out.printf("Set AccessTier on blob completed with status code %d%n", setTierResponse2.getStatusCode()); System.out.printf("Set AccessTier on blob with lease completed with status code %d%n", setTierWithLeaseResponse.getStatusCode());
When interacts with blobs using this Java client library, errors returned by the service correspond to the same HTTP
status codes returned for REST API requests. For example, if you try to retrieve a container or blob that
doesn't exist in your Storage Account, a
404 error is returned, indicating
Default HTTP Client
All client libraries by default use the Netty HTTP client. Adding the above dependency will automatically configure the client library to use the Netty HTTP client. Configuring or changing the HTTP client is detailed in the HTTP clients wiki.
Default SSL library
All client libraries, by default, use the Tomcat-native Boring SSL library to enable native-level performance for SSL operations. The Boring SSL library is an uber jar containing native libraries for Linux / macOS / Windows, and provides better performance compared to the default SSL implementation within the JDK. For more information, including how to reduce the dependency size, refer to the performance tuning section of the wiki.
Get started with our Blob Batch samples:
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact email@example.com with any additional questions or comments.