Hi Ryan,
For the pace, yes, it's what I saw with the previous release date. My
proposal is to clearly state that on website (on release page),
something like "We target a release per quarter". Just to inform the
community.
About the other points:
2.1. Great, thanks !
2.2. Yes, release notes on re
Great to have this release out! Thanks for being release manager, Anton!
And a huge thanks to everyone who contributed. It's great to see all of the
improvements.
On Fri, Oct 6, 2023 at 11:29 AM Anton Okolnychyi
wrote:
> I'm pleased to announce the release of Apache Iceberg 1.4.0!
>
> Apache Ic
The Iceberg community has already established a regular release cadence,
which is once per quarter. Here's the recent release history, minus patch
releases:
- 1.4.0: 2023-10-04
- 1.3.0: 2023-05-26
- 1.2.0: 2023-03-20
- 1.1.0: 2022-11-29
- 1.0.0: 2022-10-14
- 0.14.0: 2022-07-16
As you can see, we'
I'm pleased to announce the release of Apache Iceberg 1.4.0!
Apache Iceberg is an open table format for huge analytic datasets. Iceberg
delivers high query performance for tables with tens of petabytes of data,
along with atomic commits, concurrent writes, and SQL-compatible table
evolution.
I understand wanting to keep more in general, that's why we have the 100
column threshold set fairly high. But in the case you're describing those
column stats are causing a problem. I'd expect you to be able to drop some
of them on such a large table to solve the problem, rather than filter them
o
Hi guys,
I would like to propose some improvements on our release.
1. Predictable & regular release pace
We started this discussion quickly on the 1.4.0 vote thread: I think
it would be interesting for the community (both our users and also
companies leveraging Iceberg in their products) to have
