apache / apache/iceberg-cpp

[Discussion] Remove meson build support

オープン
#930 コメント 7 件 リアクション 1 件 担当者 0 名 GitHub で見る
主要言語
C++
スター
221
フォーク
124
平均マージ
1日 16時間
マージ済み PR(30日)
21

説明

I would like to propose removing meson build support from iceberg-cpp.

We currently have meson build support for:

- iceberg: the core library
- iceberg_data: the data reading and writing layer
- iceberg_rest: the REST catalog client

But sadly, meson support is still not aligned with CMake, missing modules include iceberg_bundle (Arrow, Avro, and Parquet integrations), the Hive catalog, and the SQL catalog.

A major challenge is that we do not seem to have enough meson expertise available for ongoing maintenance and review. AI can help us write build definitions quickly, but we still need knowledgeable reviewers to verify that the changes work correctly across supported configurations and for downstream consumers.

For example, I used AI to help implement PR #912, which aims to align meson's library modules with CMake. The implementation was relatively quick, but the PR has not received any reviews so far. Without sufficient meson expertise, it is difficult to gain confidence in the implementation and maintain it over time.

Meanwhile, we run meson CI jobs on Linux, Windows, and macOS. These consume CI resources and require maintenance even though our meson support remains incomplete. Apache Iceberg already has limited CI capacity, so I think we should consider whether maintaining a second build system is a worthwhile use of those resources.

As far as I am aware, we do not currently have users relying on Meson to build iceberg-cpp. Given the maintenance burden, limited review capacity, and CI cost, I propose removing the meson build and associated CI jobs.

If you are using meson to build iceberg-cpp, or are willing to help maintain and review its build support, please share your use case and thoughts. All feedback and alternative suggestions are welcome.

cc @wgtmac @manuzhang @WillAyd @abnobdoss @HuaHuaY

コントリビューションガイド

このリポジトリのコントリビューションガイドは索引されていません

調査の方向性

まず issue の議論と PR #912 を読み、現在の Meson モジュールと CMake との提案された整合化について理解します。Meson のビルド定義と Linux、Windows、macOS の CI ジョブを確認します。完了とは、プロジェクトが削除に合意し、Meson サポートと関連する CI ジョブが維持されなくなった状態を指します。

索引モデルが issue の本文から書いたものです。

評価

技術スタック
cmake, cpp
領域
build-system, ci-cd
issue の種類
リファクタリング
難易度
4/5
見積もり時間
3〜5日
活発さ
活発
明瞭さ
おおむね明確
初心者へのやさしさ
35/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。