Skip to content
master
Switch branches/tags
Code

Latest commit

* Clean up blank lines

* Explain how to assume-role on AWS S3 in the Spark metadata client

Also document Hadoop 3 support in Spark 3.1.2+, reformat some tables, and
correct some links.

Push this after publishing 0.1.7 (currently we only pushed 0.1.7-RC.0).

* Fix <div> structure
442a89a

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
api
 
 
 
 
cmd
 
 
 
 
 
 
 
 
 
 
pkg
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Apache License Go tests status Node tests status Integration tests status Artifact HUB code of conduct

What is lakeFS

lakeFS is an open-source tool that transforms your object storage into a Git-like repository. It enables you to manage your data lake the way you manage your code.

With lakeFS you can build repeatable, atomic, and versioned data lake operations - from complex ETL jobs to data science and analytics.

lakeFS supports AWS S3, Azure Blob Storage, and Google Cloud Storage as its underlying storage service. It is API compatible with S3 and works seamlessly with all modern data frameworks such as Spark, Hive, AWS Athena, Presto, etc.

For more information, see the official lakeFS documentation.

Capabilities

In Development

  • Experiment - try new tools, upgrade versions, and evaluate code changes in isolation. You can get an isolated snapshot to run and compare experiments by creating a new branch of the data, while others are not exposed.
  • Debug - checkout specific commits in a repository’s commit history to materialize consistent, historical versions of your data.
  • Collaborate - leverage isolated branches managed by metadata (not copies of files) to work in parallel.

During Deployment

  • Version Control - deploy data safely with CI/CD workflows borrowed from software engineering best practices. Ingest new data onto an isolated branch, perform data validations, then add to production through a merge operation.
  • Test - define pre-merge and pre-commit hooks to run tests that enforce schema and validate properties of the data to catch issues before they reach production.

In Production

  • Roll Back - recover from errors by instantly reverting data to a former, consistent snapshot of the data lake. Choose any commit in a repository’s commit history to revert in one atomic action.
  • Troubleshoot - investigate production errors by starting with a snapshot of the inputs to the failed process.
  • Cross-collection Consistency - provide consumers multiple synchronized collections of data in one atomic, revertable action.

Getting Started

Using Docker Compose (Linux/Mac)

Use this section to learn about lakeFS. For a production-suitable deployment, see the docs.

  1. Ensure you have Docker and Docker Compose installed on your computer.

  2. Run the following command:

    curl https://compose.lakefs.io | docker-compose -f - up
  3. Open http://127.0.0.1:8000/ in your web browser to set up an initial admin user. You will use this user to log in and send API requests.

Other quickstart methods

You can try lakeFS:

Setting up a repository

Once lakeFS is installed, you are ready to create your first repository!

Community

Stay up to date and get lakeFS support via:

More information

Licensing

lakeFS is completely free and open-source and licensed under the Apache 2.0 License.