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.