Re: [DISCUSS] Move iceberg-cpp step forward

2025-03-26 Thread Renjie Liu
Thanks Xuanwo for the summary. I think it's a good idea to move c/cpp related code to iceberg-cpp repo, and have a try on the cxx binding approach. On Wed, Mar 26, 2025 at 6:54 PM Junwang Zhao wrote: > Hi xuanwo > > On Tue, Mar 25, 2025 at 2:36 PM Xuanwo wrote: > >> After a deeper discussion w

Re: [DISCUSS] Move iceberg-cpp step forward

2025-03-26 Thread Junwang Zhao
Hi xuanwo On Tue, Mar 25, 2025 at 2:36 PM Xuanwo wrote: > After a deeper discussion with friends in the Slack #cpp channel, we > reached the following consensus: > >- iceberg-rust won't maintain any c/cpp related code. >- iceberg-cpp will have an internal crate based on iceberg-rust and

Re: [DISCUSS] Move iceberg-cpp step forward

2025-03-24 Thread Xuanwo
After a deeper discussion with friends in the Slack #cpp channel, we reached the following consensus: • iceberg-rust won't maintain any c/cpp related code. • iceberg-cpp will have an internal crate based on iceberg-rust and invokes cxx/cbingen to build bindings • And finally, we will have a `l

Re: [DISCUSS] Move iceberg-cpp step forward

2025-03-18 Thread Fokko Driesprong
Hi Xuanwo, Thanks for bringing this up. I'm not a cpp expert, but following this with great interest. I think this is a very promising approach since the memory model is already the same across projects (Arrow). Kind regards, Fokko Op vr 14 mrt 2025 om 08:53 schreef Xuanwo : > Hi, everyone > >

[DISCUSS] Move iceberg-cpp step forward

2025-03-14 Thread Xuanwo
Hi, everyone Today, Renjie Liu and I had a discussion with some of the iceberg-cpp contributors—Gang Wu, Junwang Zhao, and David Li—about ways to advance the project. We came up with some great ideas, so I'm sharing them here to gather more feedback. ## Background The community continues to s