apache/beam

[Feature Request]: Expose pvalue.Row in core.py rather than pvalue.py

Open

#35,095 建立於 2025年5月30日

在 GitHub 查看
 (6 留言) (0 反應) (2 負責人)Java (7,313 star) (4,097 fork)batch import
P2good first issuenew featurepython

描述

What would you like to happen?

It's semantically confusing that Row is defined in pvalue.py. pvalues are abstract representations of data while Rows are actually concretely instantiated.

It might make more sense to put it in core.py? (with a lingering alias in pvalue.py for backwards compatibility)

Issue Priority

Priority: 2 (default / most feature requests should be filed as P2)

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam YAML
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Infrastructure
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner

貢獻者指南

技術棧
python
領域
developer experience
議題類型
refactor
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
PythonApache Beam Python SDK
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
This issue proposes moving the Row class from pvalue.py to core.py for semantic clarity, while keeping a backward compatible alias. First, review the current definition of Row in sdks/python/apache beam/pvalue.py. Then, examine core.py at sdks/python/apache beam/core.py to find an appropriate location. The move involves copying the class, adding an alias in pvalue.py (e.g., from core import Row), and updating all imports across the codebase. Check for any circular import issues. The issue has 2 assignees, so coordinate with them before starting.