Nebula.Net client library is very old

[porscheme]

Please check the FAQ documentation before raising an issue

Describe the bug (required)
Nebual.Net client library is very old

Since its mostly contains auto generated code, please document how to generate the library

@wey-gu please help us.

[wey-gu]

Dear @porscheme

We could talk about this on https://github.com/nebula-contrib/nebula-net about this topic? The 3.x interface did't change as I recall, thus the client of .net should work, did you encounter any issues?

To generate code for the thrift code of RPC, we could refer to https://github.com/vesoft-inc/nebula-python/blob/master/docs/how-to-update-interface.md .

Thanks!

[porscheme]

• We have a need to steam graph query results back the dotnet/csharp client over gRpc
• Therefor, we wanted to expose a gRpc endpoint which internally uses Nebula.Net
• We did a PoC, it works fine
• Just want to make if something has change since Nebula.Net was checked-in

[wey-gu]

Aha, got it. The current dotNet client doesn't require re-generation of thrift as in our versioning policy, there are no break/RPC interface changes in 3.x. It's not been updated for some time but still valid/in good shape.

We have a need to steam graph query results back the dotnet/csharp client over gRpc

That's an interesting arch, maybe in the future, you could share with the community how the graph infra was designed and run in your system :D

Thanks~