repowiserepowise
Sign in
datazip-inc/olake
OverviewDocsArchitectureKnowledge GraphFilesCode HealthSecurityRefactoring

People & History

CommitsContributorsDecisions
Chat
Stats
repowiserepowise
ExplorePricingDocs
Sign in
repowisedatazip-inc/olake
OL
OL

datazip-inc / olake

OLake - Fastest Databases, Kafka & S3 Replication to Apache Iceberg with Table optimization (Called OLake Fusion). ⚡ Efficient, quick and scalable data ingestion for real-time analytics. Supported sources : Postgres, MongoDB, MySQL, Oracle, MSSql, DB2, Kafka, S3.

Go★ 1,466
Use in your agentAsk this codebase

github.com/datazip-inc/olake·Indexed at de2b96e·23h ago·Up to date with upstream

About this codebase

OLake Go is a codebase documentation engine for data-lake ingestion: it consumes source-DB change streams or backfills plus target lakehouse configuration, then runs a sync pipeline that produces Iceberg-native artifacts (or Plain Parquet) with exactly-once delivery semantics, surfaced through the OLake Go UI and optional CLI automation. It’s used by teams who want to replicate transactional systems—like PostgreSQL/MySQL/MongoDB/Oracle/DB2/MSSQL—into open lakehouse formats without building or operating Spark/Flink/Debezium-style infrastructure.

Written by gpt-5.4-nano from the index

374 files and 3,058 symbols in 10 modules, led by Go (237 files) and Java (33).

Start reading

  • Knowledge graph374 files and how they depend on each other.→
  • Iceberg Java Runtime IntegrationDocumentationDocumentation for destination/iceberg/olake-iceberg-java-writer/src/main/java/io/olake/iceberg, written by gpt-5.4-nano.→
  • Contributors24 people: who owns what, and where one person holds most of the knowledge.→

Code health

6.4out of 10Fair

This codebase scores 6.4 out of 10 for code health, which we rate fair. It also scores maintainability 6.9 and static performance 9.7 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 36 of 374 files are git hotspots, and they average 3.7 — which is where the fixes pay off most.

Full health report →

Do next

1 thing worth doing in the week to Sep 29, the last indexed commit, 1 of them now.

Now

  • Critical

    Clean up what this week's commits left: 7 serious findings in 6 files

    1 commit in the last 7 days added or worsened them, and they are still open. Start with destination/iceberg/olake-iceberg-java-writer/src/main/java/io/olake/iceberg/rpc/OlakeRowsIngester.java, which has 1 critical.

    serious findings
    7
    critical
    1
    files
    6
    Medium effort

Improve what Repowise can see

  • Add a test coverage report

    Without one, Repowise cannot tell tested code from untested code, so every test-related action says “unknown”.

    line coverage
    Unknown, no report
    Small effort
All actions in the Overview →

Use datazip-inc/olake in your agent

Point Claude Code, Cursor, Codex or VS Code at this repository. Your agent gets the index this page is built from: cited answers, callers, history and health for any file.

https://api.repowise.dev/mcp/datazip-inc/olake

One command, run anywhere. Adds the server to your local Claude Code config.

Docs
bash
claude mcp add --transport http repowise https://api.repowise.dev/mcp/datazip-inc/olake \
  --header "Authorization: Bearer rw_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
The snippet shows a placeholder key. Generate one to get a copyable secret.
Sign in and create an API key to connect.Sign in

This repo is public, so anyone with a Repowise account and an API key can connect.

Try asking

  • get_overview()
  • get_answer("how is olake put together?")
  • get_why("why is olake structured this way?")

Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed.

Go deeper

  • OverviewEverything the index found, what changed this week, commits and decisions.→
  • DocumentationModule-by-module documentation, 460 pages, 27 written by a model.→
  • ArchitectureDependency graph, layers and third-party dependencies.→
  • Code healthEvery file's score, the findings behind it, tests and refactoring plans.→
  • CommitsEach commit's effect on code health, with agent provenance.→
  • ContributorsWho owns what, and where one person holds most of the knowledge.→
  • DecisionsArchitectural decisions mined from commits and pull requests.→
  • Ask this codebaseSign inGrounded answers over the indexed code.→

For maintainers

Add a badge to your README

Both badges are public, cached, and update on their own after every index. Nothing to install.

Repowise badge

Links to this page. Adding it also re-indexes the repo every week.

Repowise badge: explore code
[![repowise](https://api.repowise.dev/badge/wiki/datazip-inc/olake.svg)](https://repowise.dev/repo/datazip-inc/olake)

Code health badge

Average health across every file, straight from the latest index.

Code health badge showing the average health score out of 10
[![Code health](https://api.repowise.dev/badge/health/datazip-inc/olake.svg)](https://repowise.dev/repo/datazip-inc/olake)

How datazip-inc/olake works

OLake - Fastest Databases, Kafka & S3 Replication to Apache Iceberg with Table optimization (Called OLake Fusion). ⚡ Efficient, quick and scalable data ingestion for real-time analytics. Supported sources : Postgres, MongoDB, MySQL, Oracle, MSSql, DB2, Kafka, S3. This page is a map of the datazip-inc/olake repository, written primarily in Go, rebuilt from the source each time it is indexed. Repowise parses every symbol, computes a dependency graph, scores per-file code health from complexity, duplication, test coverage and churn, mines git history for hotspots and ownership, and lifts the architectural decisions into documentation you can read here or query through MCP.

The codebase has 374 files and 3,058 symbols in 10 modules, led by Go, Java and Shell. Code health is 6.4 out of 10, rated fair.

Use the links above to open each view, or connect this repository to your agent for grounded answers inside Claude, Cursor, Codex or VS Code.