search

vesoft-inc / nebula-flink-connector

Flink Connector for Nebula Graph
48 stars 30 forks source link

Local UT would fail caused by IP used by Nebula JAVA client is not accessible #59

Closed spike-liu closed 2 years ago

spike-liu commented 2 years ago

Read data from Flink would fail in UT. The only way I can figure out is running UT in the same docker network environment. However it would cause debug codes impossible.

@Nicole00 Would you please enlighten us here?

liuxiaocs7 commented 2 years ago

The disscussion will help.

spike-liu commented 2 years ago

The disscussion will help.

Thanks, Liu.

wey-gu commented 2 years ago

I understand that you would like to leverage your local desktop's IDE on debugging things, while the current design required a docker spawned nebula cluster to actually run java client in same docker network with nebula cluster.

The hack way would be(as java storage client get list of storaged from meta, that is domain name like storaged0) we could optionally do ssh port forwarding + dns hosts to make storaged0 being resolved to the remote server's storaged docker instance(with 9779 being exposed, too)... which is not actually practical.

I would suggest instead deploying a cluster without docker for now with the host configured as an externally accessible address.

spike-liu commented 2 years ago

I understand that you would like to leverage your local desktop's IDE on debugging things, while the current design required a docker spawned nebula cluster to actually run java client in same docker network with nebula cluster.

The hack way would be(as java storage client get list of storaged from meta, that is domain name like storaged0) we could optionally do ssh port forwarding + dns hosts to make storaged0 being resolved to the remote server's storaged docker instance(with 9779 being exposed, too)... which is not actually practical.

I would suggest instead deploying a cluster without docker for now with the host configured as an externally accessible address.

Thank you so much. You really save my day!

Only god knows how many efforts I have tried already. Such as updating ip during debug, running UT in docker, etc...however no luck so far.

I would try your solution.