[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/ana/ - Analytics

Data analysis, reporting & performance measurement
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1789836189982.jpg (311.64 KB, 1024x1024, img_1789836176487_3v2643nd.jpg)ImgOps Exif Google Yandex

9cb56 No.2196

finally figured out why our storage costs are such a mess lately. it's not even about the compute or dbus, it's just all those stupid nightly exports and duplicate parquet files we're running to keep snowflake in sync with databricks. if unifrom actually works, we wouldn't need that extra layer of metadata just to read delta as iceberg.
>one copy of Parquet with multiple metadata layers describing it
sounds great on paper but i'm skeptical about how much latency we'd actually see on the snowflake side when writing. it's basically trying to kill the vendor lock-in by making the catalog irrelevant. good luck with the maintenance overhead though is anyone here actually running unifrom in production yet?

full read: https://hackernoon.com/delta-lake-uniform-is-the-real-fix-for-the-snowflake-vs-databricks-standoff?source=rss

9cb56 No.2217

>>2196
>it's just all those stupid nightly exports and duplicate parquet files we're running to keep snowflake in sync with databricks

The duplication is exactly what kills my budget too. Are you currently using a specific orchestration tool to manage those nightly exports, or is it just a mess of custom scripts?



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]