top | item 45923327 (no title) matt123456789 | 3 months ago It is not a chicken and egg problem, it is just a requirement to have an RDBMS available for systems like DuckLake and Hive to store their catalogs in. Metadata is relatively small and needs to provide ACID r/w => great RDBMS use case. discuss order hn newest dsp_person|3 months ago What about file-based catalogs with Iceberg? Found one that puts it in a single json file: https://github.com/boringdata/boring-catalog saxenaabhi|3 months ago Then concurrency suffers since you have to have locks when you update files.That's also why ducklake performs better than others.For many use cases this trade-off is worth it.
dsp_person|3 months ago What about file-based catalogs with Iceberg? Found one that puts it in a single json file: https://github.com/boringdata/boring-catalog saxenaabhi|3 months ago Then concurrency suffers since you have to have locks when you update files.That's also why ducklake performs better than others.For many use cases this trade-off is worth it.
saxenaabhi|3 months ago Then concurrency suffers since you have to have locks when you update files.That's also why ducklake performs better than others.For many use cases this trade-off is worth it.
dsp_person|3 months ago
saxenaabhi|3 months ago
That's also why ducklake performs better than others.
For many use cases this trade-off is worth it.