Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

datalake_agent: Polaris (REST) catalog

未关闭
#2,015 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
c, docker, spark

调研方向

Start by reading B3 (#2008) and the CatalogManagementService scope, then run the conformance setup against Apache Polaris or the Iceberg REST fixture with MinIO. Done means the acceptance checks pass: bidirectional Spark visibility, correct DROP behavior, and exactly one snapshot after a retried timeout.

由索引模型根据 Issue 内容生成。

描述

datalake

Part of #2008. Letters (A, B0–B7, C, D, E) are the PRs listed there; this is B5.

Scope

The first external catalog provider.

  • RESTCatalog: OAuth2 client credentials or bearer token, warehouse, vended credentials so a volume can be omitted. polaris accepted as an alias of rest, as in the fdw whitelist.
  • Commit through the catalog's CAS; B3's operation_id store covers the in-doubt window between "committed" and "the client heard".
  • Drop with and without purge; namespaces through CatalogManagementService.
  • End-to-end against Apache Polaris (or the Iceberg REST fixture image) plus MinIO in docker.
Out of scope

Hive, Hadoop. Anything the REST spec leaves optional and Polaris does not serve.

Depends on

B3.

Acceptance
  • Conformance suite green against Polaris; a table Cloudberry creates is visible to Spark in the same catalog, and the reverse.
  • DROP TABLE with and without purge_on_drop behaves as the option says.
  • A commit retried after a simulated timeout yields exactly one snapshot.
主要语言
C
星标
1.4k
派生
248
平均合并
4 天 10 小时
30 天内合并 PR
40

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

apache/cloudberry 的其他 Issue

查看 apache/cloudberry 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。