Hi Ajantha,

https://github.com/apache/iceberg/pull/12318 made JSON un-pretty for
reduing the file size.

BR,
Yuya

On Thu, May 22, 2025 at 1:52 PM Ajantha Bhat <ajanthab...@gmail.com> wrote:

> Hi Russell,
>
> Just observed this change (table metadata JSON file is not formatted
> anymore)
> https://github.com/apache/iceberg/issues/13122
>
> If it is induced by 1.9.0, we should probably fix it and include it in RC?
> No functional impact.
>
> - Ajantha
>
> On Thu, May 22, 2025 at 4:49 AM Russell Spitzer <russell.spit...@gmail.com>
> wrote:
>
>> Hi Y'all,
>>
>> I propose that we release the following RC as the official Apache Iceberg
>> 1.9.1 release.
>>
>> The commit ID is f40208ae6fb2f33e578c2637d3dea1db18739f31
>> * This corresponds to the tag: apache-iceberg-1.9.1-rc1
>> * https://github.com/apache/iceberg/commits/apache-iceberg-1.9.1-rc1
>> *
>> https://github.com/apache/iceberg/tree/f40208ae6fb2f33e578c2637d3dea1db18739f31
>>
>> The release tarball, signature, and checksums are here:
>> * https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.9.1-rc1
>>
>> You can find the KEYS file here:
>> * https://downloads.apache.org/iceberg/KEYS
>>
>> Convenience binary artifacts are staged on Nexus. The Maven repository
>> URL is:
>> *
>> https://repository.apache.org/content/repositories/orgapacheiceberg-1202/
>>
>> Please download, verify, and test.
>>
>> Please vote in the next 72 hours.
>>
>> [ ] +1 Release this as Apache Iceberg 1.9.1
>> [ ] +0
>> [ ] -1 Do not release this because...
>>
>> Only PMC members have binding votes, but other community members are
>> encouraged to cast
>> non-binding votes. This vote will pass if there are 3 binding +1 votes
>> and more binding
>> +1 votes than -1 votes.
>>
>> ---
>>
>> For those watching the big change between this and RC0 was the reversion
>> of code which
>> caused the rest client to emit multiple Snapshot Removals Requests in the
>> same MetadataUpdate.
>> This restores the behavior to that of 1.8.X, 1 removal per update.
>> We plan to move to the new behavior in a later release
>>
>

Reply via email to