apache/beam

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

Open

#35,095 opened on May 30, 2025

View on GitHub
 (6 comments) (0 reactions) (2 assignees)Java (7,313 stars) (4,097 forks)batch import
P2good first issuenew featurepython

Description

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

Contributor guide

Tech stack
python
Domain
developer experience
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
PythonApache Beam Python SDK
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
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.
[Feature Request]: Expose pvalue.Row in core.py rather than pvalue.py · apache/beam#35095 | Good First Issue