IMPORTANT: Code of Nebula go client has been transferred from nebula-clients to this repository(nebula-go), and new releases in the future will be published in this repository. Please update your go.mod and imports correspondingly.
Official Nebula Go client which communicates with the server using fbthrift. Currently the latest stable release is v2.6.0
The code in master branch will be updated to accommodate the nightly changes made in Nebula Graph. To Use the console with a stable release of Nebula Graph, please check the branches and use the corresponding version.
| Client version | Nebula Service Version |
|---|---|
| v1.0.0 | 1.x.x |
| v2.0.0-ga | 2.0.0-ga, 2.0.1 |
| v2.5.1 | >=2.5.0 |
| v2.6.0 | >=2.6.0 |
| master | 2.x-nightly |
Please be careful not to modify the files in the nebula directory, these codes were all generated by fbthrift.
NOTE Installing Nebula Go v2.5.0 could cause checksum mismatch, use v2.5.1 instead.
// For 2.x version
$ go get -u -v github.com/vesoft-inc/nebula-go/v2@master
// For 1.x version
$ go get -u -v github.com/vesoft-inc/nebula-go/@masterYou can specify the version of Nebula-go by substituting <tag> in $ go get -u -v github.com/vesoft-inc/nebula-go@<tag>.
For example: $ go get -u -v github.com/vesoft-inc/nebula-go/v2@v2.5.1
Note: You will get a message like this if you don't specify a tag:
$ go get -u -v github.com/vesoft-inc/nebula-go/v2@master go: github.com/vesoft-inc/nebula-go/v2 master => v2.0.0-20210506025434-97d4168c5c4dHere the
20210506025434-97d4168c5c4dis a version tag auto-generated by Github using commit date and SHA. This should match the latest commit in the master branch.
Nebula GO is under Apache 2.0 license, so you can freely download, modify, and deploy the source code to meet your needs. You can also freely deploy Nebula GO as a back-end service to support your SaaS deployment.
In order to prevent cloud providers monetizing from the project without contributing back, we added Commons Clause 1.0 to the project. As mentioned above, we fully commit to the open source community. We would love to hear your thoughts on the licensing model and are willing to make it more suitable for the community.