Anurag-S1ngh commented on PR #41335:
URL: https://github.com/apache/beam/pull/41335#issuecomment-6997711642

   Yes, in a narrow sense. Before the change, nested fields came through as 
Python repr (e.g. {'a': 1, 'b': True}), so anyone parsing them with 
ast.literal_eval or comparing against the repr string would see different 
output and would need to switch to json.loads. Everything else is unchanged: 
the column is still Optional[str], primitive values are byte-identical, and the 
CSV path is unaffected. The repr was not valid JSON and not a documented 
contract, so the PR treats it as the bug rather than a supported format. I have 
updated the CHANGES.md entry to call the behavior change out explicitly so it 
is visible in the release notes. I do not think an opt-out flag is worth it for 
output that was unparseable.


-- 
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