Releases: Backblaze/b2-sdk-java
v6.3.0
v6.2.1
Update CHANGELOG.md and gradle.properties for 6.2.1 release (#198)
v6.2.0
DEV-23981: Update version number for release (#194)
v6.1.1
[6.1.1] - 2022-11-10
Added
- Return a subtype of
B2Exception
on errors when the response body does not conform toB2ErrorStructure
.
Returning aB2Exception
subtype enables theB2Retryer
to retry exceptions that may succeed on retry.
Fixed
- Fixed B2ListFilesIterableBase assuming a response with 0 results was the end. It now looks for
nextFileName
being null to indicate the end.
v6.1.0
[6.1.0] - 2022-09-19
Added
- Added support for Java 8's
-parameters
option so constructor parameters do not need to be reiterated inB2Json.constructor#params
- Added
fileLockEnabled
toB2UpdateBucketRequest
to support enabling file lock on existing buckets
v6.0.0
[6.0.0] - 2022-06-03
Changed [Incompatible]
- Updated
includeExistingFiles
to be required on B2ReplicationRule
Added
- Updated to version
1.15
ofcommons-codec
.
v5.1.0
Added
- Added
s3ApiUrl
toB2AccountAuthorization
. - Updated to version
4.5.13
oforg.apache.httpcomponents:httpclient
- Updated to version
4.13.2
ofjunit:junit
- Added Replication Configuration to Create Bucket and Update Bucket API requests/responses
v5.0.0
Changed [Incompatible]
- Disabled automatic decompression of compressed content in HTTP client download library
- Added
updateFileRetention
andupdateLegalHold
toB2StorageClient
- Added
storeLargeFileFromLocalContentAsync
toB2StorageClient
to support asynchronous large file uploads
Added
- Added Server-Side Encryption (SSE) support to relevant API requests/responses
- Added File Lock support to relevant API requests/responses
- Set gradle targetCompatibility to 1.8
- Added support for java.util.SortedMap interface
- Support more than 64 fields per object
Fixed
- Fixed regular expression that had an unescaped '.'
v4.0.0
features:
- Removed the deprecated okhttp client
- Added 'readBuckets' and 'listAllBucketNames' application key capability names
- Added the "Expect: 100-continue" header to upload file/part requests
- Validates file info header name characters against RFC 7230 (https://tools.ietf.org/html/rfc7230#section-3.2)
- B2Json:
Add general generics support to B2Json
Allow generic types for top-level objects from select entry points
Add support for parameterized classes that contain generic arrays
Add support for CharSequence
Add an omitNull parameter to @B2Json.optional - Disabled URI normalization in Apache HttpClient
- Extended B2FileVersion and B2Part to include contentMd5
- Added support to override additional download headers
- Added optional 'options' parameter in the B2Bucket and B2ApplicationKey constructor
- Added b2_copy_file support
- Added progress reporting in the B2LargeFileStorer
fixed:
- See the closed issues for a complete list
v.3.1.0
features:
-
added @B2Json.sensitive annotation to redact fields when B2Json is
used with the new redactSensitive option set to true. -
added B2ContentSource.createContentSourceWithRangeOrNull() which
is used by the large file uploader to give the content source the
opportunity to make a more efficient content source for a range of
the file. this is really useful if the content isn't coming from
memory or a local file because the default implementation reads
and discards data to get to the desired range. Added sample
UploadLargeFileFromUrl and UrlContentSource. -
added support for using okhttp3 as the HTTP client instead of
Apache's HttpClient. there are limitations with this
implementation for uploading files that are about 2GB or
larger. see README.md for details. -
added B2StorageClientFactory interface for creating
B2StorageClients without having to select a particular
implementation at build time. The static createDefaultFactory()
method can be used to create a B2StorageClient using either of the
two official web client implementations, whichever is in the
classpath at runtime. The sample programs use this now so they
can be used with either web client implementation.
other improvements:
- don't use default character set in B2Json; explicitly use UTF8.