seatunnel
seatunnel copied to clipboard
apache
[Feature][Connector-V2]new connecotor of TiKV source and sink
Purpose of this pull request
Add new new connecotor of TiKV source and sink, refer to https://github.com/apache/incubator-seatunnel/issues/1946#issuecomment-1253260625.
Check list
- [x] Code changed are covered with tests.
- [x] If any new Jar binary package adding in your PR, please add License Notice according New License Guide
- [ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs
Can you add doc to introduce this connector? Reference: https://github.com/apache/incubator-seatunnel/tree/dev/docs/en/connector-v2
And tell the user why implementing in Java client is better than JDBC, or the different between two way.
And tell the user why implementing in Java client is better than JDBC, or the different between two way.
sure 😃
@Hisoka-X I have fixed some code style issues, please rerun ci workflow again
You can package in local before you push. So you can find problem eariler.
Ok, thanks, I'm testing locally and there are still some trouble, so don't review the code first.
The simple scenario test passed, but there are still some types that are not compatible, and there are still some problems in requesting tidb in the docker environment. I am dealing with
@Xuxiaotuan hi，I am currently completing the e2e of Tidb, but when I use Docker to start the cluster, there is always a problem with the connection between PD and Tidb. Do you know the reason
[util.rs:549] ["PD failed to respond"] [err="Grpc(RpcFailure(RpcStatus { code: 14-UNAVAILABLE, message: "failed to connect to all addresses", details: [] }))"] [endpoints=127.0.0.1:2379]
@Xuxiaotuan hi，I am currently completing the e2e of Tidb, but when I use Docker to start the cluster, there is always a problem with the connection between PD and Tidb. Do you know the reason
[util.rs:549] ["PD failed to respond"] [err="Grpc(RpcFailure(RpcStatus { code: 14-UNAVAILABLE, message: "failed to connect to all addresses", details: [] }))"] [endpoints=127.0.0.1:2379]
when accessing between tidb pd and tikv, it is accessed through the internal address side, similar to hadoop xxx:port
@Xuxiaotuan hi，I am currently completing the e2e of Tidb, but when I use Docker to start the cluster, there is always a problem with the connection between PD and Tidb. Do you know the reason [util.rs:549] ["PD failed to respond"] [err="Grpc(RpcFailure(RpcStatus { code: 14-UNAVAILABLE, message: "failed to connect to all addresses", details: [] }))"] [endpoints=127.0.0.1:2379]
when accessing between tidb pd and tikv, it is accessed through the internal address side, similar to hadoop xxx:port
https://mp.weixin.qq.com/s/36EzhuTVb6oiUZTUYSJMWg tidb is currently accessible in docker
I checked and found that when start only tikv and pd, docker is required to use host-network-mode-linux Because I am using macOS, I encountered some problems, in fact，“The host networking driver only works on Linux hosts, and is not supported on Docker Desktop for Mac, Docker Desktop for Windows, or Docker EE for Windows Server.”
@Xuxiaotuan hi，I am currently completing the e2e of Tidb, but when I use Docker to start the cluster, there is always a problem with the connection between PD and Tidb. Do you know the reason [util.rs:549] ["PD failed to respond"] [err="Grpc(RpcFailure(RpcStatus { code: 14-UNAVAILABLE, message: "failed to connect to all addresses", details: [] }))"] [endpoints=127.0.0.1:2379]
when accessing between tidb pd and tikv, it is accessed through the internal address side, similar to hadoop xxx:port
https://mp.weixin.qq.com/s/36EzhuTVb6oiUZTUYSJMWg tidb is currently accessible in docker
Thank you. I'll try that, too