+1, Thanks for XinYu.
Great work!

> 2026年5月14日 12:55,Jingsong Li <[email protected]> 写道:
> 
> Thanks Xinyu and your team!
> 
> +1 for this. We can create a sub-project of Paimon under Apache, split
> the PRs and review them one by one, and then merge them into the
> repository. During this process, I am willing to provide assistance
> for review.
> 
> Best,
> Jingsong
> 
> On Thu, May 14, 2026 at 12:00 PM 刘欣瑀 <[email protected]> wrote:
>> 
>> Hi Paimon community,
>> 
>> I'd like to start a discussion about contributing paimon-cpp to the Apache 
>> Paimon project. We'd love to hear any feedback or suggestions from the 
>> community.
>> 
>> 
>> 
>> About paimon-cpp
>> 
>> Paimon-cpp is a high-performance C++ implementation of Apache Paimon, 
>> developed by the Storage Service team at Alibaba. It is currently hosted at  
>> https://github.com/alibaba/paimon-cpp  under the Apache License 2.0. The 
>> goal is to provide a native C++ library that allows native engines to access 
>> Paimon lakehouse tables with high efficiency and less overhead.
>> 
>> 
>> 
>> 
>> Feature Overview
>> 
>> The library supports append table and primary key table write, commit, scan, 
>> read and compaction. It uses Apache Arrow columnar format for 
>> high-throughput batch operation, supports ORC/Parquet/AVRO file formats, and 
>> provides pluggable format, file system, memory pool, metrics, and thread 
>> pool abstractions. It also supports DataEvolution mode for AI scenarios and 
>> various index types. It is compatible with Apache Paimon's format and 
>> protocol (manifests, commit messages, data splits).
>> 
>> 
>> 
>> 
>> Motivation
>> 
>> Bringing paimon-cpp under the Apache Paimon project would help maintain 
>> consistent format semantics, reduce the risk of ecosystem fragmentation, and 
>> foster collaborative, cross-language development within the community.
>> 
>> 
>> 
>> 
>> Questions
>> 
>> We welcome any feedback, questions, or suggestions regarding the donation 
>> process.
>> 
>> 
>> 
>> 
>> Best regards,
>> 
>> Xinyu Liu

Reply via email to