HNHacker News
TopNewBestAskShowJobs

talatuyarer

39 karma · joined March 19, 2018

submissionscomments
talatuyarer··on Show HN: Public Apache Iceberg datasets via a REST catalog
I hope this helps you

https://gist.github.com/talatuyarer/02568a38a7630434556e7dc1...

talatuyarer··on Show HN: Public Apache Iceberg datasets via a REST catalog
Thank you.

Yes We have plan to publish Dataset for Apache V3 spec features such as Variant, Deletion Vector. I can update this comment when we have release date.

talatuyarer··on Lessons from Running Apache Iceberg in Production at Uber and DoorDash
I believe link is wrong. Please use this to enroll: https://luma.com/byyyrlua
talatuyarer··on The Line Between Databricks and BigQuery Just Got Blurry with BigLake MetaStore
An architectural deep dive into how Google’s BigLake Metastore unifies Databricks and BigQuery through open standards — without vendor lock-in.
talatuyarer··on Apache Iceberg V3 Spec new features for more efficient and flexible data lakes
I believe we are very close to release candidate. We are waiting unknown type support for Apache Spark per latest email

https://lists.apache.org/thread/gd5smyln3v6k4b790t5d1vy4483m...

talatuyarer··on Apache Iceberg V3 Spec new features for more efficient and flexible data lakes
Yes, the specification will be finalized with version 1.10. Previous versions also include specification changes. Iceberg's implementation of V3 occurs in three stages: Specification Change, Core Implementation, and Spark/Flink Implementation.

So far only Variant is supported in Spark and with 1.10 Spark will support nano timestamp and unknowntype I believe.

talatuyarer··on Apache Iceberg V3 Spec new features for more efficient and flexible data lakes
Yes 1.10 version will be first version for V3 spec. But not all features are implemented on runners such as Spark or Flink.
talatuyarer··on Apache Iceberg V3 Spec new features for more efficient and flexible data lakes
This new version has some great new features, including deletion vectors for more efficient transactions and default column values to make schema evolution a breeze. The full article has all the details.