-
Notifications
You must be signed in to change notification settings - Fork 335
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BitSail][Connector] Migrate Kafka legacy connector to V1 interface #113
Comments
@john8628 assigned to you, thanks! |
@garyli1019 Is this task not assigned yet, I want to try |
Hi @liuxiaocs7 , how's everything going with this issue? |
@garyli1019 sorry for late, I have learned about Kafka and the implementation of Flink-Kafka-connector. I will continue this issue after the completion of #336, any progress will be let you know and discussed here. :) |
Hi @liuxiaocs7 , I have a task blocked by this feature and I need to get this done in the next two days. If you don't mind, may I take this over? |
Sorry for late, @garyli1019, you can continue to take over, recently I've been busy with my master's degree opening matters and my graduate advisor's project, I did some of the work before #393 , you see if it helps you a little, if not please ignore it. If I can do anything, please let me know and I will enhance this connector together. |
@liuxiaocs7 I will only work on the sink connector, so you can resume the kafka source work when you have time. Really appreciate your contribution! |
sink part: #395 |
OK, thanks for your help, i will finish kafka-source as soon as possible |
Is your feature request related to a problem? Please describe
We want to migrate the legacy kafka connector to V1 interface. Similar with #98 for redis
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: