apache/rocketmq-externals

[rocketmq-connect-hudi] sinkConnectConfig topicRouteMap not set value

Open

#856 创建于 2021年12月14日

在 GitHub 查看
 (0 评论) (0 反应) (0 负责人)Java (4,513 star) (3,084 fork)batch import
good first issue

描述

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

BUG REPORT

  1. Please describe the issue you observed:
  • What did you do (The steps to reproduce)?

org.apache.rocketmq.connect.hudi.connector.HudiSinkConnector

defaultKeyValue.put(HudiConnectConfig.CONN_TOPIC_ROUTE_INFO, JSONObject.toJSONString(sinkConnectConfig.getTopicRouteMap()));

image

  • What did you expect to see? sinkConnectConfig.getTopicRouteMap() should set org.apache.rocketmq.connect.hudi.connector.HudiSinkConnector#topicRouteMap

  • What did you see instead? sinkConnectConfig.topicRouteMap no set value

  1. Please tell us about your environment:

  2. Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):

FEATURE REQUEST

  1. Please describe the feature you are requesting.

  2. Provide any additional detail on your proposed use case for this feature.

  3. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?

  4. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:

贡献者指南

技术栈
java
领域
databackend
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Familiarity with RocketMQ ConnectJava debugging skills
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
Examine the HudiSinkConnector class in the rocketmq connect hudi module. The issue reports that sinkConnectConfig.topicRouteMap is not being assigned to the connector's topicRouteMap field. Check the start() or configure() method to ensure the field is properly populated from configuration. The fix likely involves adding an assignment like this.topicRouteMap = sinkConnectConfig.getTopicRouteMap() in the appropriate initialization block.