Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Manohar Pothapragada
Fix slow Apache Iceberg ™ queries caused by small files, with Table Optimizer
Show video transcript This query reads one customer's events from the past four weeks from an Apache Iceberg table. It takes about thirty-seven seconds. Let's see how we can optimize the same query on the same table to be faster - without any change to the query itself. So… why does the query become slow? The cause is… small files, accumulated over time. When data lands in small, frequent batches, each batch adds a few small files.
See how much of your Spark compute sits idle
Spark Analyzer: See how much of your Spark compute sits idle When you submit an Apache Spark™ job, you set how many executors it gets and how many cores each one has. You pay for those cores from the moment the executors start until the job ends, whether tasks run on them or not. Most teams never find out how much of that time the cores sat idle. Cost Analyzer for Apache Spark measures it. It’s a free Python tool that you run on your own machine.
Query lakehouse tables from a Python client with Lakegres
Onehouse Lakegres: Query lakehouse tables from a Python client Onehouse Lakegres™ gives your lakehouse tables a Postgres endpoint. That means the Python tools you already use, such as psycopg2, SQLAlchemy, pandas and polars, can read those tables directly, with the same code you would write against any Postgres database. In this post, we connect a small Python script to Lakegres two ways: with the Postgres driver, and with the Onehouse Python SDK.
Near real-time Oracle CDC, without pipeline firefighting
Show video transcript Change data capture from Oracle means bringing every insert, update and delete into an open table, readable as Iceberg, within minutes. When built by hand, it's a lot of work. That means: resolving every insert, update and delete in the right order, such that nothing is lost or duplicated and also ensuring that the table delivers low-latency queries.
Setting up Onehouse on any Kubernetes, with Autosetup
Setting up Onehouse on any Kubernetes, with Autosetup Onehouse Bring-Your-Own-K8s runs the Onehouse data plane on your own Kubernetes cluster, next to the rest of your stack, and keeps your tables in your own bucket. Onehouse runs the control plane. Setting it up used to mean an eight-step runbook. With Autosetup, you run one command and your AI coding agent walks you through the rest: the onehouse-autosetup skill checks the cluster, asks before every change and ends with a working data plane.
MySQL CDC to Parquet tables on S3, with Kafka set up for you
Show video transcript A ticketing site keeps every seat for tonight's show in MySQL. At ten a.m., twenty thousand seats go on sale. The show-day ops team wants to see which sections are selling out, right now. But their analytics tables load only once a night. A seat goes from free, to held, and eventually to sold. Or… back to free, when a checkout times out. We need every change as it happens. That's change data capture, or CDC.
Quarantine bad records without stopping your Postgres CDC pipeline
Onehouse OneFlow: One bad record shouldn’t stop your pipeline Every pipeline eventually meets a record it shouldn’t load: a timestamp from the future, a value that breaks a business rule, a row that doesn’t match the expected structure. What happens next decides whether your morning starts with a stale dashboard, a wrong report, or nothing at all.
Postgres CDC to Parquet tables on S3, with PII masking, in a few clicks
October 22, 2026 TL;DR Onehouse OneFlow turns a live Postgres table into Parquet tables on Amazon S3 with one Postgres CDC source and one flow, both created in the console and with no pipeline code. The Mutable write mode applies inserts, updates and deletes to the existing rows, Data Masking hashes customer emails before anything is written, and Pipeline Quarantine sets bad records aside.
Postgres schema evolution without pipeline changes
October 22, 2026 TL;DR When a column is added to a Postgres table, Onehouse OneFlow carries it into the Parquet tables on Amazon S3 on the next sync, without editing, redeploying or backfilling the pipeline. In our run, a coupon_code column added with ALTER TABLE was queryable in the Parquet table about 6 minutes later.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Manohar
Contact Manohar, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack