Java Storage Client Library 10.0.4-rc

• Support for the 2017-11-09 REST version. Please see our REST api documentation and blogs for information about the related added features.

• Support for 2018-03-28 REST version. Please see our REST api documentation and blogs for information about the related added features.

• Support for the getAccountInfo api on ServiceURL, ContainerURL, and BlobURL.

• Added support for setting service properties related to static websites.

• Changed BlobURL.startCopy sourceAccessConditions parameter to be HTTPAccessConditions as lease is not actually supported.

• Added methods to TransferManager for conveniently downloading a blob to a file.

• UploadFromFile now takes an AsynchronousFileChannel.

• UploadByteBuffersToBlockBlob, UploadByteBufferToBlockBlob, and DownloadToBuffer have been removed.

• IPRange fields are now strings.

• Fixed retry policy.

• Fixed logging policy.

Java Storage Client Library 10.0.3-Preview

• Resolved dependency issues

Java Storage Client Library 10.0.2-Preview

• Support for 2017-07-29 REST version. Please see our REST api documentation and blogs for information about the related added features.

• Support for setting a block blob's tier.

• Added support for soft delete feature. If a delete retention policy is enabled through the set service properties API, then blobs or snapshots can be deleted softly and retained for a specified number of days, before being permanently removed by garbage collection.

• Changed BlobListingDetails constructor to take a flag to include deleted blobs.

• Restructured the blob and container listing responses.

• BlockBlobURL.MAX_PUT_BLOCK_BYTES renamed to BlockBlobURL.MAX_STAGE_BLOCK_BYTES.

Java Storage Client Library 10.0.1-Preview

• Added the RetryReader class to allow for more reliable streaming on large downloads. This is now the return type of blobURL.download

• Fixed a bug that caused generation of signatures to fail at high levels of parallelism.

• Created the StorageException type to give easy access to the ErrorCode, StatusCode, and Message as available for unsuccessful responses.

• Added the StorageErrorCode type for checking against error codes returned by the service.

• Changed the AppendBlobAccessConditions field types to be Long instead of Int.

• Upgraded Netty dependency to allow uploading memory mapped files with https.

• Upgraded the autorest runtime dependency to fix a dependency bug in their package.

• Changed RequestRetryOptions maxTries and tryTimeout fields to be Integer instead of int. 0 is no longer allowed.

• Changed CommonRestResponse.lastModifiedTime to be lastModified.

• Added statusCode property to CommonRestResponse.

• Change dateProperty to be date on all generated types.

• Fixed a bug that prevented proper reset of body stream upon retry.

• Updated the defaults for RequestRetryOptions.

Java Storage Client Library 8.0.0

• Support for 2018-03-28 REST version. Please see our REST API documentation and blogs for information about the related added features.
• Added support for static website properties.
• Added support for the getAccountInfo feature. Sku name and account kind may be retrieved using a CloudBlobClient, CloudBlobContainer, or CloudBlob with SharedKey or SAS.
• Added support for putBlockFromURI. A block may be created with another block blob as its source.
• Upgraded the language version to Java 7.
• Updated the Jackson-Core dependency to version 2.9.4 to pull in security fix.

Java Storage Client Library 7.1.0-Preview

• Support for 2017-11-09 REST version. Please see our REST API documentation and blogs for information about the related added features.
• Added OAuth token support for authentication with HTTPS requests.
• Support for write-once read-many containers.

Java Storage Client Library 10.0.0-Preview

• Initial Release. Please see the README and wiki for information on the new design.

Java Storage Client Library 7.0.0

• Support for 2017-07-29 REST version. Please see our REST api documentation and blogs for information about the related added features.
• Added support for soft delete feature. If a delete retention policy is enabled through the set service properties API, then blobs or snapshots can be deleted softly and retained for a specified number of days, before being permanently removed by garbage collection.
• When a storage request fails, the error code may now be retrieved directly from the RequestResult and StorageException classes. This error code is populated even in cases where there is no StorageExtendedErrorInformation available, such as in calls to FetchAttributes.
• Queue messages may now be inserted with infinite duration by specifying -1 as the timeToLiveInSeconds parameter to addMessage.
• Improved performance of blob uploadFromFile APIs to avoid unnecessary buffering.
• Improved performance when streaming directly from a FileInputStream to avoid unnecessary buffering.
• Switched to using fixed length streaming mode in the HTTP client to avoid unnecessary buffering.
• Upgraded Key Vault dependency to 1.0.
• Fixed a bug preventing openInputStream from working on a blob snapshot.

Java Storage Client Library 6.1.0

• Added support for the last time the tier was modified.

Java Storage Client Library 6.0.0

• Added support for taking a snapshot of a share.
• IOExceptions wrapping StorageExceptions will now contain the StorageException message in the outer exception.
• Connection string support expanded to allow AccountName to be specified with SharedAccessSignature and DefaultEndpointsProtocol. In this case, SharedAccessSignature is used for credentials, while having both DefaultEndpointsProtocol and AccountName allows the library to infer a set of default endpoints. Additionally, we have added support for BlobSecondaryEndpoint, QueueSecondaryEndpoint, TableSecondaryEndpoint, and FileSecondaryEndpoint. Specifying a secondary endpoint requires the specification of the corresponding primary.
• All: The use of DefaultEndpointsProtocol in a connection string is now optional in the case where endpoints would be automatically generated; if missing, a value of https will be inferred. When the parsed account settings in such a case are used to generate a connection string, the value of DefaultEndpointsProtocol will be explicitly included.