-
Notifications
You must be signed in to change notification settings - Fork 188
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
Support for OTP20+ #399
Comments
The latest release - https://github.com/basho/riak-erlang-client/tree/riak_kv-3.0.1 is OTP 20 + - so the tag Apologies the edocs, readme and release notes aren't up to date with the recent release history. I've not tried this with |
|
A OTP 20+ riak erlang client pointing at riak_kv 2.2.5 is not something I've tried to get working yet - there may be some issues with the riak_pb dependancy. I will have a look at this tomorrow. |
I didn't get chance to look at this today, in terms of actually proving anything, but having thought about it there shouldn't be any issues pointing the up-to-date riak erlang client (with OTP 20+ support) at an older version of Riak (e.g. 2.2.5). The PB API has been updated, but only with new additions, so using old functionality should not be changed. |
It worked - able to make CRUD operations, but I had to compile it independently (without including it to This is exactly what I did: When added to I'm running a Nitrogen web framework application which is still built on |
This was very useful for setting up my development environment (.... after scratching my chin a few times and going "Hmmm..."). Thanks. |
@martinsumner how can we be able to use
rebar2
inrebar.config
{deps,[]}
forriak-erlang-client
to compile on OTP20 and later ? Right now the edoc states this{riakc, "2.5.*", {git, "https://github.com/basho/riak-erlang-client", {tag, "2.5.1"}}}
, which is only supported on not later than OTP19.The text was updated successfully, but these errors were encountered: