Skip to main content

How to work with OneLake files locally using Python

Last week I shared how you could use the  OneLake File Explorer to sync your Lakehouse tables to your local machine. It's a convenient way to get your Parquet and Delta Lake files off the cloud and onto disk — but what do you actually do with them once they're there?

In this post, I’ll walk you through how to interact with your locally synced OneLake files using Python. We'll cover four practical approaches, with real code you can drop straight into a notebook.

Where are your files?

When OneLake File Explorer syncs your files, they land in a path that looks something like this:

C:\Users\<you>\OneLake - <workspace name>\<lakehouse name>.Lakehouse\Tables\<table name>

Keep that path in mind— you'll be passing it into every example below. Delta Lake tables are stored as folders containing multiple Parquet files plus a _delta_log/ directory, so make sure you're pointing at the table's root folder, not an individual file.

Reading a parquet file using Pandas

If you just need to load a parquet file into a DataFrame for analysis or transformation, pandas is the fastest way to get started.

Make sure you have Aandas and PyArrow installed:

pip install pandas
pip install pyarrow

Now you can run the following Python code

import pandas as pd

# Read a single Parquet file
df = pd.read_parquet(r"C:\Users\you\OneLake - MyWorkspace\MyLakehouse.Lakehouse\Tables\orders\part-00001.parquet")

print(df.head())
print(df.dtypes)

Pandas uses PyArrow under the hood for Parquet reading, so you get solid type handling and decent performance for most workloads. For large tables, be mindful of memory — it loads everything into RAM.



Reading delta tables using delta-rs

If your table is in Delta format (which is the default in Fabric Lakehouses), you'll want delta-rs to take advantage of Delta-specific features like schema enforcement, versioning, and time travel.

First install deltalake:

pip install deltalake

Now you can use this library to query the delta table:

from deltalake import DeltaTable

table_path = r"C:\Users\you\OneLake - MyWorkspace\MyLakehouse.Lakehouse\Tables\orders"

# Load the latest version
dt = DeltaTable(table_path)
df = dt.to_pandas()

# Check table metadata
print(dt.schema())
print(f"Current version: {dt.version()}")

Where delta-rs really shines is time travel — you can read any historical version of your table:

# Read a specific version

dt_v2 = DeltaTable(table_path, version=2)
df_v2 = dt_v2.to_pandas()

# Or go back to a point in time
from datetime import datetime
dt_yesterday = DeltaTable(table_path, version=datetime(2026, 2, 22))
df_yesterday = dt_yesterday.to_pandas()

This is invaluable when you're debugging a pipeline and need to see what the data looked like before a bad write landed.

That’s it!

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...