Hi Kevin,

On Tue, May 26, 2026 at 11:59 PM Kevin Liu <[email protected]> wrote:
>
> Great to see the upcoming release! Thanks everyone for the amazing set of 
> features.
> Please let me know if there's anything I can help with the release process :)

Thanks for chiming in, it's great to have your help :-)

>
> On Tue, May 26, 2026 at 8:52 AM Guotao Yu <[email protected]> wrote:
>>
>> Hi,
>>
>> Thanks for kicking off this discussion and for the detailed summary of 
>> what's landed since 0.2.0 — it's a solid body of work.
>>
>> I'm currently working on merging update support, which includes overwrite 
>> functionality. I'd like to request a short delay before cutting the 0.3.0 
>> release to allow this work to land. My estimate is roughly 1–2 weeks to get 
>> the overwrite support merged.
>>
>> Having overwrite as part of 0.3.0 would round out the data write story 
>> nicely alongside the existing DataWriter, PositionDeleteWriter, and delete 
>> filter support that's already in. I think it would make for a more complete 
>> release for downstream users who are looking to do full read/write workflows.
>>
>> If the timeline doesn't work for the release plan, I'm happy to discuss 
>> alternatives — but if there's flexibility, I'd appreciate the window to get 
>> this in.
>>
>> Thanks for considering it.
>>
>>
>> Junwang Zhao <[email protected]> 于2026年5月26日周二 17:24写道:
>>>
>>> Hi all,
>>>
>>> I would like to start a discussion about releasing Apache Iceberg C++ 0.3.0.
>>>
>>> We originally tracked the 0.3.0 roadmap in:
>>> https://github.com/apache/iceberg-cpp/issues/523
>>>
>>> Not every item in that roadmap has been completed yet. However, it has
>>> been a while since the 0.2.0 release(Jan 26, 2026), and there has been
>>> a meaningful amount of work merged since then. I think it is worth
>>> considering a 0.3.0 release now, rather than continuing to wait for
>>> every planned item to land.
>>>
>>> Since v0.2.0, 114 commits have landed on main. Some notable completed areas 
>>> are:
>>>
>>> - REST catalog authentication:
>>>   * No-op authentication integration
>>>   * Basic authentication
>>>   * Initial OAuth2 support
>>>
>>> - Table update and maintenance:
>>>   * SnapshotManager
>>>   * ReachableFileCleanup for expire snapshots
>>>   * IncrementalFileCleanup in ExpireSnapshots::Finalize
>>>   * ManifestFilterManager and ManifestMergeManager
>>>   * Bulk delete API in FileIO
>>>
>>> - Incremental scan planning:
>>>   * Incremental scan API
>>>   * Incremental append scan
>>>   * Incremental changelog scan
>>>   * Column selection support in table scan planning
>>>
>>> - Data write and delete-file support:
>>>   * DataWriter for Iceberg data files
>>>   * PositionDeleteWriter/EqualityDeleteWriter
>>>   * DeleteLoader for position and equality delete files
>>>   * Position delete index and roaring-based position bitmap
>>>   * Delete filter support
>>>   * MOR file scan task reader
>>>
>>> - FileIO and object-store support:
>>>   * S3 FileIO integration
>>>   * Streaming FileIO support
>>>
>>> - Format and type support:
>>>   * JSON serde for expression operations and expressions
>>>   * v3 timestamp nanosecond primitive types
>>>   * Puffin basic data structures, constants, format utilities, and JSON 
>>> serde
>>>
>>> - Writer metrics and related improvements:
>>>   * Metrics for Avro writer
>>>   * Metrics for Parquet writer
>>>
>>> - Reliability, and infrastructure:
>>>   * Retry failed transaction commit
>>>   * Shared package linkage fixes
>>>   * CMake and Meson version alignment
>>>
>>> Given the amount of features that has already finished, I propose that
>>> we prepare a 0.3.0 release and continue the remaining roadmap work
>>> toward the next release. This would give downstream users a new stable
>>> point for the completed REST auth, table maintenance, incremental
>>> scan, data writer/delete support, S3/FileIO, and related improvements.
>>>
>>> Thoughts?
>>>
>>> --
>>> Regards
>>> Junwang Zhao
>>
>>
>>
>> --
>> Regards
>> Guotao Yu



-- 
Regards
Junwang Zhao

Reply via email to