danny0405 opened a new issue, #19246: URL: https://github.com/apache/hudi/issues/19246
### Feature Description **What the feature achieves:** the original metadata is single map serialized as JSON, switch to separate items. **Why this feature is needed:** 1. Footer metadata is already a key/value map, so JSON adds a redundant encoding layer. 2. Tools can inspect individual values without Hudi-specific JSON parsing. 3. A malformed value affects one field instead of making the entire header unreadable. 4. Schema and other JSON-valued fields avoid JSON-within-JSON escaping. 5. New fields remain backward-compatible: old readers simply ignore unknown keys. 6. The footer is written atomically with the file, so the single JSON value provides little additional atomicity. 7. Parquet already reads the complete footer, so this is mainly a cleaner contract—not an I/O optimization. ### User Experience **How users will use this feature:** no explicit options. - Configuration changes needed - API changes - Usage examples ### Hudi RFC Requirements **RFC PR link:** (if applicable) rfc-103 **Why RFC is/isn't needed:** - Does this change public interfaces/APIs? (Yes/No) - Does this change storage format? (Yes/No) - Justification: -- 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]
