apache/beam

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

Open

Aperta il 30 mag 2025

Vedi su GitHub
 (6 commenti) (0 reazioni) (2 assegnatari)Java (7313 star) (4097 fork)batch import
P2good first issuenew featurepython

Descrizione

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

Guida contributor

Tech stack
python
Dominio
backenddeveloper experience
Tipo issue
feature
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
2
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-3 hours
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
active
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
clear
Prerequisiti
PythonGit
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
65
Direzione di ricerca
Trova la definizione corrente di Row in pvalue.py, spostala in core.py, aggiungi un alias retrocompatibile in pvalue.py e aggiorna tutte le importazioni.