Releases: buoyant-data/oxbow
Releases · buoyant-data/oxbow
v0.8.2
Identical to v0.8.1
v0.8.1
Minor bugfixes to help with timestamp issues and avoiding s3:TestEven…
v0.8.0: Introduce an advanced deployment with the group-events lambda
The grouo-events lambda helps serialize S3 Bucket Notifications into SQS FIFO such that modifications to specific delta table paths in S3 are handled generally in sequence to reduce lock contention. More discussed [in this blog post](https://www.buoyantdata.com/blog/2023-11-27-concurrency-limitations-with-deltalake-on-aws.html)
v0.7.1
Fixing the lock key formatting
v0.7.0: Incorporate fixes in the deltalake v0.16.5 release and many bug fixes
Probably the most significant change is that the Lambda will fail if there is any other error when accessing the Delta Table other than `NotATable`. This helps identify potentially corrupted or invalid Delta Tables, without oxbow attempting to convert the prefix to a table (and ultimately failing). This release also incorporates some improvements in lock handling and logging
v0.6.2
Use a unique lock key for each table modified by oxbow (#9)
v0.6.1: Identical to 0.6.0 Release with a pinned transitive dependency
This release includes a change in the dynamodb-lock crate which ensures that locks have a valid TTL and are reaped appropriately.
v0.5.0
Ensure that there is no panic in a critical locked section, issue #5
v0.4.0
Avoid adding redundant files, which can come from eventually consiste…
v0.3.0
Bump to version 0.3.0 for another release