---
title: "László Hadházy (@lhadhazy) | Hashnode"
description: "Data platform engineer at Cordata. Read the latest articles by László Hadházy on Hashnode."
url: "https://hashnode.com/@lhadhazy"
---

@lhadhazy

# László Hadházy

@lhadhazy · Budapest, Hungary · Joined August 2026

Data platform engineer at Cordata.

[Website](https://cordata.tech/)

### [Green pipeline, broken page — deploying full-stack Rust](https://cordata.hashnode.dev/green-pipeline-broken-page-deploying-full-stack-rust?utm_source=hashnode&utm_medium=feed)

Formatting, linting and every asset URL came back green on a page whose main button was invisible. What a Rust deploy pipeline can and cannot check.

23 min read · [cordata.hashnode.dev](https://cordata.hashnode.dev/green-pipeline-broken-page-deploying-full-stack-rust?utm_source=hashnode&utm_medium=feed)

[Sep 18](https://hashnode.com/posts/green-pipeline-broken-page-deploying-full-stack-rust/6aad4f0f455090fe3a6b21b6)

### [Snowflake external lineage keeps addressing, not meaning](https://cordata.hashnode.dev/snowflake-external-lineage-keeps-addressing-not-meaning?utm_source=hashnode&utm_medium=feed)

Snowflake ingests OpenLineage now. It keeps where the data came from and discards why it was processed — which decides what you can build on it.

16 min read · [cordata.hashnode.dev](https://cordata.hashnode.dev/snowflake-external-lineage-keeps-addressing-not-meaning?utm_source=hashnode&utm_medium=feed)

[Sep 17](https://hashnode.com/posts/snowflake-external-lineage-keeps-addressing-not-meaning/6aab91f3de07f45dec8134db)

### [The descriptor survived, const did not — full-stack Rust](https://cordata.hashnode.dev/descriptor-survived-const-did-not?utm_source=hashnode&utm_medium=feed)

A replication with a control: the same claim re-run in Rust, and the property that looked like the point did not survive.

20 min read · [cordata.hashnode.dev](https://cordata.hashnode.dev/descriptor-survived-const-did-not?utm_source=hashnode&utm_medium=feed)

[Sep 9](https://hashnode.com/posts/descriptor-survived-const-did-not/6aa1009b6b79f1cec285fc75)

### [The trace\_id was the easy part — Rust, OTel, Loki](https://cordata.hashnode.dev/the-trace-id-was-the-easy-part-rust-otel-loki?utm_source=hashnode&utm_medium=feed)

Adding a trace\_id to your logs is the last of four things that must be true. The other three fail silently — and produce telemetry that looks correct right up until someone needs it.

18 min read · [cordata.hashnode.dev](https://cordata.hashnode.dev/the-trace-id-was-the-easy-part-rust-otel-loki?utm_source=hashnode&utm_medium=feed)

[Aug 30](https://hashnode.com/posts/the-trace-id-was-the-easy-part-rust-otel-loki/6a9400269b7d296ea3aa866b)

### [One port, three client crates — a hexagonal Rust ingester](https://cordata.hashnode.dev/one-port-three-client-crates?utm_source=hashnode&utm_medium=feed)

One trait survived alloy, solana-client and subxt 0.50 — three crates that agree on nothing.

19 min read · [cordata.hashnode.dev](https://cordata.hashnode.dev/one-port-three-client-crates?utm_source=hashnode&utm_medium=feed)

[Aug 27](https://hashnode.com/posts/one-port-three-client-crates/6a902c6e38601307a80f0af5)
