Skip to content
DEDataEngUtils

DataEngUtils for Data Engineers

Data Engineers build and maintain the infrastructure that moves, transforms and stores data. The daily work involves Parquet and Avro files, warehouse SQL, dbt YAML, connection strings and pipeline schedules — and the usual tool for each is a website that uploads your production data to someone else's server. DataEngUtils runs the whole toolbox in your browser on a Rust engine compiled to WebAssembly, so files are read locally and never uploaded. This page maps the tools most relevant to Data Engineers onto the workflows you run every week.

Tools for data engineers

Workflow: Inspect and query Parquet

Open a Parquet file in the browser to read its schema, row groups and column statistics, then query and export a slice — all without a warehouse, a notebook, or an upload.

  1. 1. Drop the Parquet file

    Open Parquet Inspector and add the file. The Apache Arrow engine reads the footer and schema locally in a Web Worker.

  2. 2. Query and profile

    Use Parquet Query to select columns and filter rows, or Parquet Data Profiler for nulls, ranges and distributions per column.

  3. 3. Export the result

    Send the slice to CSV, Parquet or JSON, and copy the stats into a ticket.

Workflow: Convert and merge files

Turn CSV exports into columnar Parquet, export Parquet back to CSV, and merge several extracts into one dataset — processed locally in your browser.

  1. 1. Add your CSV files

    Open CSV → Parquet and drop files in. Delimiters and preamble rows are auto-detected and adjustable.

  2. 2. Choose compression

    Pick Snappy, Zstd or Gzip and preview the schema before writing.

  3. 3. Download Parquet

    Save the .parquet output, then re-open it in Parquet Inspector to verify before it lands in the warehouse.

Workflow: Validate dbt and warehouse SQL

Catch dbt YAML mistakes and format or explain warehouse SQL without a full dbt run or a web beautifier.

  1. 1. Validate dbt YAML

    Paste a schema.yml excerpt into the dbt YAML Validator to catch structure and indentation errors before CI.

  2. 2. Format the SQL

    Drop a CTE-heavy query into the SQL Formatter and pick the dialect for consistent casing and indentation.

  3. 3. Explain the query

    Use SQL Query Explainer to list the tables, joins, CTEs and columns before you optimize.

Workflow: Debug schemas, secrets and schedules

Diff two pipeline schema versions for compatibility, split connection strings with the password masked, and read cron schedules in plain language.

  1. 1. Check schema evolution

    Load the before and after Parquet files into Parquet Schema Evolution to see added, removed and retyped columns with a compatibility verdict.

  2. 2. Split a connection string

    Paste a postgres:// or kafka:// URI into the Connection String Parser to review host, database and parameters with the password masked.

  3. 3. Read a cron schedule

    Drop the expression into the Cron Expression Parser for a description, the next ten runs and a heatmap.

Frequently asked questions

Does DataEngUtils replace dbt or a query engine?
It complements them. It validates dbt YAML, formats SQL and inspects Parquet locally. For project-wide compilation you still run dbt, and for full SQL on Parquet you might use DuckDB — DataEngUtils is the fast, no-setup check in between.
Are my Parquet files uploaded?
No. The app has no backend. Files are read by a Rust engine (Apache Arrow) compiled to WebAssembly and run in a Web Worker, so the bytes never leave your device.
Is the Parquet workbench free?
The Parquet Inspector, Row Group Pruner and Parquet → JSON are free. Query, Data Profiler, Schema Evolution, File Repair and CSV → Parquet are Pro, unlocked with a one-time licence from $39.