rangareddy commented on issue #17262: URL: https://github.com/apache/hudi/issues/17262#issuecomment-5365807773
This issue was reviewed as part of the JIRA-migrated backlog triage (HUDI-7861). **Findings: not resolvable by code inspection alone.** The MDT schema is version-aware in places today: `HoodieIndexVersion.getCurrentVersion` returns V1 or V2 per metadata partition type based on `HoodieTableVersion`, and column stats, partition stats and expression index all switch to V2 at table version 9. So the mechanism the ticket asks for partly exists. What I could not establish by reading is whether the specific requirement holds - a bridge-release (0.16) reader successfully consuming a metadata table written by 1.0.0 that contains one or more of the newer MDT partitions. That is a cross-version compatibility test, not a code property. Note also the description opens with "old:", which suggests the scope was already rewritten once; it would help to state the current intent. Keeping this open. -- 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]
