rangareddy commented on issue #17340: URL: https://github.com/apache/hudi/issues/17340#issuecomment-5351234738
This issue was reviewed as part of the JIRA-migrated backlog triage (HUDI-8732). **Findings: still open, but this ticket cannot be actioned as written.** The GitHub body carries only the JIRA boilerplate - there is no description of *which* upgrade/downgrade requirements or steps are considered too strict, and no acceptance criteria. That makes it impossible to verify against the current code or to hand to a contributor. Its siblings under HUDI-9106 in this same batch are concrete and could serve as the anchor for scoping this one: - #17336 (HUDI-8702) - `table update-configs` leaves `hoodie.record.merge.strategy.id` stale - #17339 (HUDI-8731) - no guard forbidding a merge-mode change Could whoever owns HUDI-9106 add the intended scope here - specifically which steps in the current upgrade/downgrade flow are the ones to relax, and what the target user experience is? Without that this is not workable. Keeping this open pending scope. -- 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]
