-
Notifications
You must be signed in to change notification settings - Fork 66
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
How to use v2.0.2 version in project #98
Comments
@mixadior you're totally right and we've still not added an /v2 folder that is required due to the major version bump.
I've tested with this simple example that uses an v2.0.2 added function:
Let's keep this issue open until we fix this issue and release v2.0.3 with the proper folder struct. Thank you for reporting it! |
Hi, thx for fast response. https://github.com/RediSearch/redisearch-go/blob/master/go.mod :
latest release is 1.8.3 , i'm not so fluent in go modules, but seems redigo v2.0.0 is left from migration and is orphaned - gomodule/redigo#366 |
@mixadior It seems that when we enabled go modules, for some reason that was the version that I was working with on a48d16f . One very interesting thing is that we kicked off go mod support pretty much at the same time across other redislabs projects ( example of redistimeseries-go https://github.com/RedisTimeSeries/redistimeseries-go/blob/master/go.mod ) and it seems that for some reason I did a bad version update on this one... ( on timeseries is as expected ) |
@filipecosta90 interesting )), redigo 2.0.0 has last commit in 2018. Probably it will be better to change go.mod file to redigo v1.8.3 , because redisearch is compatible with v1.x.x of redigo and everything should work ok. Anyway, thx. |
Hi there @mixadior, we've just released v1.1.0 that should have all fixes we've discussed. Once again thank you for raising this issue :) |
Hi, all
i try to add
bash-3.2$ ./go.sh get -d github.com/RediSearch/[email protected] go get: github.com/RediSearch/[email protected]: invalid version: module contains a go.mod file, so major version must be compatible: should be v0 or v1, not v2 bash-3.2$
but it failed with error.
The text was updated successfully, but these errors were encountered: