The case for an iceberg-native database
warpstream.com
The case for an iceberg-native database
1–6 of 6 posts
Re: The case for an iceberg-native database
#2While not related to the topic exactly, the blur under the translucent header was so distracting I had trouble reading the article. Usually I can overlook stuff like this; I can't explain why it bothered me so much.
Re: The case for an iceberg-native database
#3Kinda off-topic but I love the quality of images used in this article. Even memes are HD. Quite rare as people tend to use whatever meme creator provides - super-pixelated, low-quality source image with text slapped on top.
Re: The case for an iceberg-native database
#4While not related to the topic exactly, the blur under the translucent header was so distracting I had trouble reading the article. Usually I can overlook stuff like this; I can't explain why it bothered me so much.
the problem really is that if you scroll you have enough variation between images and text it makes the translucent header function as a sort of blink effect, calling your attention away from what you're trying to read which is probably right up by where the header is blinking.
Re: The case for an iceberg-native database
#5The main selling point of the open table formats is to decouple the data from query engines.
Re: The case for an iceberg-native database
#6Isn't that almost what we got with DuckDB + DuckLake?