OpenMetadata Warehouse
In development prototypeI connected Claude Code to an OpenMetadata service running over an Oracle and SQL Server warehouse, so ingestion, lineage and server lifecycle are managed as code.
An OpenMetadata implementation over a two-engine institutional warehouse (Oracle + SQL Server): connectors, data dictionaries, lineage, and the server's own lifecycle managed as code, with Claude Code driving the metadata service directly.
Technology
- ETL & databases
- Automation
Sector
- Public sector
- Health
Problem
A public-sector health insurer's data warehouse spans two database engines with no shared catalogue: nobody can see where a field came from, or what feeds a report, without asking whoever built it originally. Lineage and data dictionaries only ever existed in people's heads.
What it will be
A case study on standing up OpenMetadata over a real institutional warehouse: connectors for both engines, generated data dictionaries, lineage from source table to report, and the server's own lifecycle — upgrades, backups, restarts — managed as code rather than by hand. Claude Code drives the metadata service directly, which doubles as evidence for how this workspace actually uses it day to day.
Status: Being documented and anonymised for public release. Demo and code follow.