You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by "hjtran (via GitHub)" <gi...@apache.org> on 2025/05/30 14:03:44 UTC
[I] [Feature Request]: Expose pvalue.Row in core.py rather than pvalue.py [beam]
hjtran opened a new issue, #35095:
URL: https://github.com/apache/beam/issues/35095
### What would you like to happen?
It's semantically confusing that `Row` is defined in `pvalue.py`. `pvalue`s are abstract representations of data while `Row`s 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
- [x] 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
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature Request]: Expose pvalue.Row in core.py rather than pvalue.py [beam]
Posted by "CH-Abhinav (via GitHub)" <gi...@apache.org>.
CH-Abhinav commented on issue #35095:
URL: https://github.com/apache/beam/issues/35095#issuecomment-6111409519
Hi @damccorm, I noticed PR #37071 was closed because moving Row introduces breaking risks without sufficient justification. If we leave Row's definition in `pvalue.py` to preserve serialization and simply re-export it in `apache_beam.transforms.core` (or keep it solely as `beam.Row`), would that be desirable, or should we close this issue as not planned?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature Request]: Expose pvalue.Row in core.py rather than pvalue.py [beam]
Posted by "HarshYadav1159 (via GitHub)" <gi...@apache.org>.
HarshYadav1159 commented on issue #35095:
URL: https://github.com/apache/beam/issues/35095#issuecomment-4369182624
.take-issue
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature Request]: Expose pvalue.Row in core.py rather than pvalue.py [beam]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #35095:
URL: https://github.com/apache/beam/issues/35095#issuecomment-3456305010
This issue has been marked as stale due to 150 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that’s incorrect or this issue still needs to be addressed, please simply write any comment. If closed, you can reopen the issue at any time. Thank you for your contributions.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature Request]: Expose pvalue.Row in core.py rather than pvalue.py [beam]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #35095:
URL: https://github.com/apache/beam/issues/35095#issuecomment-5931860414
This issue has been marked as stale due to 150 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that’s incorrect or this issue still needs to be addressed, please simply write any comment. If closed, you can reopen the issue at any time. Thank you for your contributions.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature Request]: Expose pvalue.Row in core.py rather than pvalue.py [beam]
Posted by "nikitagrover19 (via GitHub)" <gi...@apache.org>.
nikitagrover19 commented on issue #35095:
URL: https://github.com/apache/beam/issues/35095#issuecomment-3615912172
Hi @hjtran ! I'd like to work on this issue as my first contribution to Apache Beam.
I read through the ticket and took a quick look at the current implementation. I agree with the reasoning here — 'pvalue.py' mostly contains abstractions around pipeline values, while `Row` is a concrete, user-facing structure, so its placement does feel a bit out of place. Moving it into 'core.py' with a compatibility alias in 'pvalue.py' seems like the right general direction.
At a first glance, this looks doable, but I want to spend some time going through the code layout and imports properly before making any changes, just to make sure nothing unexpected breaks.
Let me know if there’s anything specific I should keep in mind as I dive deeper into it. Thanks!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature Request]: Expose pvalue.Row in core.py rather than pvalue.py [beam]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #35095: [Feature Request]: Expose pvalue.Row in core.py rather than pvalue.py
URL: https://github.com/apache/beam/issues/35095
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature Request]: Expose pvalue.Row in core.py rather than pvalue.py [beam]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #35095:
URL: https://github.com/apache/beam/issues/35095#issuecomment-3585683540
This issue has been closed due to lack of activity. If you think that is incorrect, you can reopen the issue at any time.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature Request]: Expose pvalue.Row in core.py rather than pvalue.py [beam]
Posted by "damccorm (via GitHub)" <gi...@apache.org>.
damccorm commented on issue #35095:
URL: https://github.com/apache/beam/issues/35095#issuecomment-6125695518
Lets close the issue, thanks
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature Request]: Expose pvalue.Row in core.py rather than pvalue.py [beam]
Posted by "nikitagrover19 (via GitHub)" <gi...@apache.org>.
nikitagrover19 commented on issue #35095:
URL: https://github.com/apache/beam/issues/35095#issuecomment-3615914741
.take-issue
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature Request]: Expose pvalue.Row in core.py rather than pvalue.py [beam]
Posted by "HarshYadav1159 (via GitHub)" <gi...@apache.org>.
HarshYadav1159 commented on issue #35095:
URL: https://github.com/apache/beam/issues/35095#issuecomment-4369161193
Hi @hjtran , I would like contribute to this issue. Thanks!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature Request]: Expose pvalue.Row in core.py rather than pvalue.py [beam]
Posted by "damccorm (via GitHub)" <gi...@apache.org>.
damccorm closed issue #35095: [Feature Request]: Expose pvalue.Row in core.py rather than pvalue.py
URL: https://github.com/apache/beam/issues/35095
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org