No I'm not. Because the people who need this mentality shift are also people who won't listen anyway and have a negative attitude. And the people who already understand this don't need to see this article.
Iceberg is not Snowflake originated, it was built by folks at Netflix - the same folks who built Tabular.
But yes, this is definitely bad for Snowflake, Databricks can position itself as a very strong competitor with this move and moving more towards Iceberg.
So this makes it sound like a positive thing for Iceberg as a format. Others seem to be suggesting that DataBricks will be working to undermine the format in favor of their older Delta Lake format but that seems overly cynical.
My guess is Data Bricks saw the popularity of Iceberg and realized that they were starting to look a little irrelevant still trying to promote their competing Delta Lake format. Have an Iceberg lakehouse? Well then Databricks just didn't seem very relevant to you. With their purchase of Tabular they're given some legitimacy when they start marketing their products as being iceberg compatible. This doesn't signal to me that Iceberg is going to be harmed in the near or medium term.
Interesting, foreign key constraints typically make sharding harder, interesting to see them add support for some type of fkey constraint (even though it's same-shard only) to the db. I wonder how it impacts use-cases like vreplication/online DDL - I suppose you have to be careful with the exact semantics of the fkeys.
Also, there are many a decent xysicists in tech. Physics skews to supernerds like good CS folks, so there's quite a bit of problem-solving and subject matter crossover beyond the closest neighbor, EE/CS.
The Goog has pockets of okayness here and there, so maybe they've found a comfortable home after 12 years. :)
reply