[Fix] [Kafka Source] kafka source use topic as table name instead of fullName#8401
Conversation
eab9490 to
29a2ddb
Compare
29a2ddb to
428e2f6
Compare
c88c3ad to
643f82c
Compare
| String topic = readonlyConfig.get(TOPIC).replace(".", "_"); | ||
| TablePath tablePath = TablePath.of("kafka", topic); |
There was a problem hiding this comment.
Hi why not use TablePath.of("kafka", readonlyConfig.get(TOPIC))?
There was a problem hiding this comment.
If the kafka topic name contains more than 3 points, when this line of code is executed, it will still be separated by points. If the element is greater than 3, IllegalArgumentException will still be thrown
There was a problem hiding this comment.
I think we should fix it. We can save the TablePath directly instead of the corresponding string in SinkFlowLifeCycle.
There was a problem hiding this comment.
I tried to save the TablePath before, but it involved other files and many of them were modified
There was a problem hiding this comment.
Never mind. Please commit it then we can review it together.
61686ed to
25f720b
Compare
25f720b to
8754e65
Compare
| // String tableId = | ||
| // action.getConfig().getMultipleRowTableId(); |
There was a problem hiding this comment.
| // String tableId = | |
| // action.getConfig().getMultipleRowTableId(); |
| @AllArgsConstructor | ||
| public class SinkConfig implements Config { | ||
| private String multipleRowTableId; | ||
| // private String multipleRowTableId; |
There was a problem hiding this comment.
| // private String multipleRowTableId; |
|
Overall LGTM. Let's waiting to check the ci result. |
Hisoka-X
left a comment
There was a problem hiding this comment.
But you lost the change of kafka and test case.
ok, I will delete the comment code you just mentioned and add kafka test case |
0d3b5fd to
38e5925
Compare
38e5925 to
b0f4bc9
Compare
| DEFAULT_FIELD_DELIMITER, | ||
| null); | ||
| generateTestData(serializer::serializeRow, 0, 100); | ||
| generateTestData(serializer::serializeRow, 0, 10); |

Purpose of this pull request
resolve #8396
Does this PR introduce any user-facing change?
How was this patch tested?
Check list
New License Guide
release-note.