rangareddy commented on issue #17010: URL: https://github.com/apache/hudi/issues/17010#issuecomment-5391444370
This issue was reviewed as part of the JIRA-migrated backlog triage (HUDI-9428). **Findings: still open.** **The premise of this ticket is currently false: Spark 3.3 support has not been removed.** The root `pom.xml` still declares an `<id>spark3.3</id>` profile with `spark33.version` 3.3.4. The history is worth recording, because it is not linear: support was **dropped** by PR #18786 (`facb517ef957`, 2026-05-21) and then **reintroduced** by PR #18956 (`7c934f10f89b`, 2026-06-13). So the precondition this cleanup waits on was briefly true and has since been reversed. Partial progress on the concrete item does exist: `ResolveHudiAlterTableCommand` is now split into `BaseResolveHudiAlterTableCommand` (`hudi-spark-common`), `Spark3ResolveHudiAlterTableCommand` (`hudi-spark3-common`) and `Spark4ResolveHudiAlterTableCommand` (`hudi-spark4-common`) - so a shared base did move to spark-common as the description asked, with per-major-version subclasses that are reasonable while both lines are supported. Recommend either re-scoping this to "reduce hudi-sparkX duplication across the currently supported lines" or parking it until a 3.3 removal actually sticks. As written it will not be actionable. **One note to avoid a mis-triage:** the PR referenced here, #12772 (`[HUDI-7915] Spark 4 support`), **is merged** (2025-09-22) - but that is the change this ticket follows up on, not a fix for it. 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]
