After more than 3 years since its initial public release...
🎉 lakeFS 1.0 is now generally available 🎉
This is a huge milestone for the lakeFS maintainers, contributors and community and we can't be more excited!
Benefits
1.0 is more than just a cosmetic change - it includes a few important benefits and guarantees to anyone running or using lakeFS:
- lakeFS 1.x ensures both backwards and forwards compatibility with any future 1.x release, as per Semver.
- Not just the lakeFS Open API: This is also true for the new lakeFS Python SDK, the Java SDK and the lakectl CLI tool.
- Bug fixes will be released for lakeFS 1.x even after the release of future major version, and at least until October 2024
- Security fixes will be released (and if needed, backported) even after the release of future major version, and at least until June 2025(!).
- While lakeFS is already trusted in production in hundreds of organizations around the world, 1.x ensures a stable API going forward and it is highly recommended for all lakeFS users.
Feature Highlights
The lakeFS 1.0 release actually doesn't introduce any new capabilities other than the guarantees given above. However,
for users of slightly older 0.x lakeFS versions, here are a few highlights from the last few months that are included with this version:
lakectl local- Allows syncing a local directory with remote data in lakeFS, including full Git integration (read announcement)- iceberg catalog - Making it possible to branch, commit and merge multiple Iceberg tables together and in tandem with other formats (read announcement)
- lua based hooks - Run your own custom logic when commits, merges and other events occur. No need to host a webhook server or deploy anything! (read announcement)
- enhanced security with pre-signed URLs - Allows lakeFS to version data it cannot even read! This enhanced security by leveraging pre-signed URLs supported on all common object stores, to allow lakeFS to authorize access to data without having to proxy that data through the lakeFS server (read more)
- Many many bug fixes and performance improvements across the board
Notes on upgrading from lakeFS 0.x
While most of the API hasn't changed much, there are a few notable API changes between 0.x and 1.x.
The migration path is usually pretty simple and not many code changes are required - but please read through the list of breaking changes: lakeFS 1.0 - Code Migration Guide
For more information on the benefits of upgrading to 1.0 and the migration path, please refer to the lakeFS documentation or reach out on Slack.
🐛 Bugs fixed: