Persist write configuration to parquet files
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.6k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 33
Description
### Describe the enhancement requested
The writer configuration influences the nature of the parquet file and often required for debugging and posterity.
Application logs are temporary and wiped after a few days.
Support configurable behaviour which can pass the writer configuration to the parquet footer optionally.
### Component(s)
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by tracing how writer configuration and Parquet footer metadata are handled, then determine the configuration shape and optional persistence behavior. Done means the selected writer configuration can be recovered from the footer when enabled, with the default behavior preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100