[Bug] Hudi writer does not inherit Hadoop configuration
维护者通常 1 天内回复
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 25/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 停滞
- 技术栈
- java
调研方向
Start where the Hudi tiering code creates HoodieFlinkWriteClient with HoodieFlinkEngineContext.DEFAULT, and compare it with how HadoopConfigurations.getHadoopConf(flinkConfig) builds the Hadoop settings from the catalog. Pull request #4584 is already open against this issue, so review that work before starting. Done means the write client's engine context carries the S3 settings, with regression tests covering both the COW and MOR paths.
由索引模型根据 Issue 内容生成。
描述
Search before asking
- I searched in the issues and found nothing similar.
Fluss version
main (development)
Please describe the bug 🐞
When Hudi tiering creates its HoodieFlinkWriteClient, it uses HoodieFlinkEngineContext.DEFAULT. The default context does not contain the Hadoop configuration assembled from the Hudi catalog configuration.
As a result, filesystem settings such as fs.s3a.endpoint, fs.s3a.access.key, and fs.s3a.secret.key are missing from the write client. Tiering to S3-compatible storage can then fail with authentication errors even though the properties are configured for the Hudi catalog.
This can be reproduced by configuring a Hudi lake catalog against S3-compatible storage and writing either a COW/log table or a MOR/primary-key table. Fluss accepts the records, but Hudi fails when accessing the remote filesystem without the configured credentials.
Expected behavior: the Hudi write client's engine context inherits the Hadoop configuration derived from the table/catalog configuration.
Solution
Construct HoodieFlinkEngineContext with HadoopConfigurations.getHadoopConf(flinkConfig) and use it to create the Hudi write client. Add regression coverage for both COW and MOR paths.
Are you willing to submit a PR?
- I'm willing to submit a PR!
- 主要语言
- Java
- 星标
- 2.2k
- 派生
- 656
- 平均合并
- 1 天 21 小时
- 30 天内合并 PR
- 127
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
apache/fluss 的其他 Issue
-
[lake/iceberg] Reserved write-mode properties can be set and reset through their `iceberg.` key可能已有人在做 @aphenix-r7 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
[common] Decimal#hashCode is inconsistent with Decimal#equals可能已有人在做 @firasbouzazi 于 13 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
[security] PlainSaslServerProvider conflicts with Hadoop SASL provider causing authentication failure可能已有人在做 @xinzhang-hello 于 19 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 1 天内回复
-
[server] KV snapshot scheduling stops permanently after a transient snapshot-init failure可能已有人在做 @zhang-arvin 于 18 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
[docs] Document advertised-resource and ACL principal ignore-case options可能已有人在做 @EchoLee5 于 31 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
scylladb/scylla-cdc-source-connector#350 ·
维护者通常 1 天内回复
-
agent:working documentation enhancement go:build lane:needs-decision
难度 2/5 1-3 小时 新手友好度 72/100
Sanne/incus-spawn#1435 · 3 条评论 ·
维护者通常 1 天内回复
-
area:shuffle bug priority:high requires-triage
难度 2/5 1-3 小时 新手友好度 72/100
apache/datafusion-comet#7062 ·
维护者通常 1 天内回复
-
wait for review
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
enhancement good first issue up-for-grabs
难度 2/5 1-3 小时 新手友好度 80/100
AnikethTS/ChangeRadar#22 ·
维护者通常 1 天内回复