Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Add optional catalog field to runs and dlchange topic schemas

未關閉
#246 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
56/100
Issue 類型
功能
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
json, postgresql, python, yaml
領域
api, backend, databases

研究方向

Start with conf/topic_schemas/runs.json and conf/topic_schemas/dlchange.json, then trace where catalog_id is persisted in the Postgres writer and database schema. Check api.yaml, related tests, documentation, and example payloads for the same field. Done when both schemas accept an optional free-form string, persistence and API handling are updated, and events without catalog remain valid.

由索引模型根據 Issue 內容生成。

描述

enhancement
Feature Description

Add an optional catalog string field to the event bus schemas (ADR 009, V4):

  • conf/topic_schemas/runs.json: inside each jobs[] item, next to catalog_id
  • conf/topic_schemas/dlchange.json: top level, next to catalog_id

Description: "Specifies the catalog name: glue, hive, starburst, etc. Since same catalog_id can exist in multiple catalogs". Free-form string; the listed values are examples, not an enum.

Problem / Opportunity

The same catalog_id can exist in multiple catalogs (glue, hive, starburst, ...), so catalog_id alone is ambiguous for consumers, dashboards and event-based triggering.

Acceptance Criteria
  1. runs.json job items and dlchange.json accept an optional catalog string.
  2. Values are not restricted to glue/hive/starburst.
  3. Events without catalog stay valid (backward compatible); the field is not added to required.
  4. Postgres writer, DB migration, api.yaml, tests and docs handle the new field (persisted wherever catalog_id is persisted).
  5. Example payloads are updated.
Proposed Solution

Add the property to both schemas, extend the writer and add a migration (nullable column), update api.yaml and tests.

Dependencies / Related

ADR 009 - Event Bus - Run and EDLA topics (V4 proposal).

主要語言
Python
星號
4
分支
0
平均合併
22 小時 3 分鐘
30 天內合併 PR
8

環境準備

  • 提供 Dockerfile 或 Docker Compose 檔案
  • 有 Pull Request 範本
  • 沒有貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

AbsaOSS/EventGate 的其他 Issue

查看 AbsaOSS/EventGate 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。