lakeFS uses a copy-on-write mechanism to avoid data duplication. For example, creating a new branch is a metadata-only operation: no objects are actually copied. Only when an object changes does lakeFS create another version of the data in the storage. For more information, see Versioning internals.
We are extremely responsive on our Slack channel, and we make sure to prioritize the most pressing issues for the community. For SLA-based support, please contact us at email@example.com.
We collect anonymous usage statistics to understand the patterns of use and to detect product gaps we may have so we can fix them. This is optional and may be turned off by setting
false. See the configuration reference for more details.
The data we gather is limited to the following:
- A UUID which is generated when setting up lakeFS for the first time and contains no personal or otherwise identifiable information,
- The lakeFS version currently running,
- The OS and architecture lakeFS is running on,
- Metadata regarding the database used (version, installed extensions and parameters such as DB Timezone and work memory),
- Periodic aggregated action counters (e.g. how many “get_object” operations occurred).
Delta Lake, Hudi, and Iceberg all define dedicated, structured data formats that allow deletes and upserts. lakeFS is format-agnostic and enables consistent cross-collection versioning of your data using Git-like operations. Read our comparison for a more detailed comparison.
The Axolotl – a species of salamander, also known as the Mexican Lake Monster or the Peter Pan of the animal kingdom. It’s a magical creature, living in a lake - just like us! :)