refactor: make convert_proto_to_parquet_flatten more memory-efficient #259
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was changed
Refactored
convert_proto_to_parquet_flattenfor better memory efficiency and faster execution and added test coverage:Implementation changes:
Test coverage (10 new tests):
Why?
The original implementation created multiple intermediate DataFrames and performed expensive concat operations for each workflow, causing high memory usage and slow activity execution on large exports. The refactor builds data more efficiently while maintaining identical output.
Checklist
How was this tested:
How was this tested: All 10 tests pass (uv run poe test
tests/cloud_export_to_parquet/test_data_trans_activities.py -v) (see test coverage above)
Any docs updates needed?
Don't think this applies.