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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to