lakesoul-io/LakeSoul

LakeSoul is an end-to-end, realtime cloud-native Lakehouse framework for fast data ingestion, concurrent updates, incremental analytics, multimodal data...

View on GitHub ↗Jump to charts ↓Open shareable report →

lakesoul-io/LakeSoul has 3k+ stars and 400+ forks on GitHub, is written in Rust, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 21st, 2026
Created on December 28th, 2021
Open Issues & Pull Requests: 19 (+0)
GitHub issues: Enabled
Number of forks: 428
Total Stargazers: 3,257 (+0)
Total Subscribers: 315 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.9 days
Mean response time: 11.6 days
90th percentile: 35.8 days
Tracked items: 51

Maintainer activity

3 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 14% of issues opened in the past year have never received a reply. 80% of issues opened in the past year have been closed, leaving a working backlog. Three people close 98% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 11
New in 7 days: 2
Closed in 7 days: 2
Avg open age: 154 days
Stale 30+ days: 8
Stale 90+ days: 6

Recent activity

Opened in 7 days: 2
Closed in 7 days: 2
Comments in 7 days: 1
Events in 7 days: 5

Top labels

  • enhancement (3)
  • rust (3)
  • dependencies (2)
  • epic (2)
  • good first issue (2)
  • bug (1)
  • flink (1)
  • java (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

LakeSoul is a cloud-native lakehouse framework that provides end-to-end data ingestion, concurrent updates, incremental analytics, and vector search capabilities for BI and AI workloads.

LakeSoul addresses the complexity of assembling production lakehouse infrastructure by delivering a batteries-included platform rather than just a table format. It solves the problem of fragmented implementations across different languages and compute engines by implementing its metadata management and file format IO entirely in Rust, then providing idiomatic bindings for Java, Python, and C++. This single high-performance core ensures that whether data is queried via Spark, streamed through Flink, or used for model training with PyTorch or Ray, all engines share identical ACID guarantees, upsert semantics, and read performance. The tool includes automated multi-level compaction, fine-grained role-based access control with S3 proxy support, high-performance OLAP queries, vector retrieval, full-text retrieval, and native multimodal data processing powered by Ray and Daft.

Teams should adopt LakeSoul when they need a production-ready lakehouse without assembling separate catalog, compaction, and authentication services. It suits organizations running mixed workloads across Spark, Flink, and Python-based ML frameworks who want consistency guarantees across all engines. The project supports multiple storage systems including HDFS and S3, and offers three physical file format modes: vortex-compact as the default, parquet, and vortex for multimodal data and vector embeddings. Unlike solutions that require maintaining per-language or per-engine reimplementations of table format logic, this approach eliminates behavioral divergences between bindings.

The project maintains active test coverage across multiple compute frameworks with dedicated test workflows for Maven, Flink CDC, native builds, and Python. Development activity spans the full stack from Rust core implementation through language bindings and integrations with major data processing ecosystems.