-
Notifications
You must be signed in to change notification settings - Fork 62
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
Protobuf message contract #63
Comments
Dear @sunkararp, Welcome to nebula community~~ Nebula GraphD now can only speak facebook thrift rather than gRPC. There is not yet .net client out there but a team in nebula hackathon is working on this :). Before .net client is ready, you could consider talk to nebula graph in .net with HTTP through nebula-http-gateway :). BR//Wey |
We tried nebula-http-gateway, here are the issues we found...
|
Dear @sunkararp Could you follow the README last tagged version(which is nsid not common-nsid)?
|
Thanks @wey-gu for the reply.
We now wanted to call Import API (/api-nebula/task/import), to bulk ingest Vertices and Edges. |
Please take a look into https://github.com/vesoft-inc/nebula-importer 's guide to make more sense of it: the bulk information it self is not in the body but in a file path that gateway can access. If that is not what you want, you could also create long ngql body with exec API instead. Please note nGQL like insert support BULK, thus we should put bulk vertex insert in one line instead of multiple lines. |
BTW, you can actually try https://github.com/shyboylpf/nebula-net , they presented in the nebula hackathon yesterday! |
We tried to use ttps://github.com/shyboylpf/nebula-net, stuck with getting below... SemanticError: The maximum number of statements allowed has been exceeded |
I saw your issue nebula-contrib/nebula-net#10 , responded there. |
We wanted to use .net core 6.0 gRpc client to interact with Nebula graph.
Questions:
The text was updated successfully, but these errors were encountered: