You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "hudi-bot (via GitHub)" <gi...@apache.org> on 2025/11/30 12:47:23 UTC
[I] Revisit catalog implementation class check [hudi]
hudi-bot opened a new issue, #17110:
URL: https://github.com/apache/hudi/issues/17110
## JIRA info
- Link: https://issues.apache.org/jira/browse/HUDI-9635
- Type: Improvement
--
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: commits-unsubscribe@hudi.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Revisit catalog implementation class check [hudi]
Posted by "rangareddy (via GitHub)" <gi...@apache.org>.
rangareddy commented on issue #17110:
URL: https://github.com/apache/hudi/issues/17110#issuecomment-5366096374
This issue was reviewed as part of the JIRA-migrated backlog triage (HUDI-9635).
**Findings: still open.**
The body carries only JIRA boilerplate - there is no statement of which catalog check is meant, what is wrong with it, or what the target behaviour is, so there is nothing to verify or hand over.
Context that probably identifies it: the Polaris catalog delegation work landed in PR #13558 (`[HUDI-9594] Allow Hudi to delegate catalog operations to Apache Polaris`, merged 2025-07-25) and introduced `hoodie.spark.polaris.catalog.class` (`DataSourceOptions.scala:300`). A class check added there is the likely subject, and #17113 (HUDI-9639) is a sibling from the same PR discussion asking for Polaris IT tests.
Could whoever filed this restate it against that - which check, and what should it do instead?
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: commits-unsubscribe@hudi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org