Riak Python Client release candidate published

Alex De la rosa alex.rosa.box at gmail.com
Wed Jul 30 14:28:03 EDT 2014


Awesome!! Can't wait to get my hands on it and Riak 2.0rc1! :)

Thanks!
Alex

On Wednesday, July 30, 2014, Sean Cribbs <sean at basho.com> wrote:

> Hey Riak Users,
>
> We've just pushed a release candidate of the official Python client to
> PyPi [1]. This package includes support for Riak 2.0.0 RC1 features,
> including security, data types, Search 2.0 (Yokozuna), and bucket
> types. Documentation on the new APIs is incomplete [2], but you can
> refer to the official Riak documentation [3] for overviews and
> tutorials with Python-specific examples. We will be polishing the API
> documentation for the final release.
>
> Please note that this release adds a new dependency on pyOpenSSL [4],
> which supports a wider range of TLS options than the standard library
> ssl package. This is only used if you enable Riak 2.0's new security
> features, but will be installed regardless when you install the
> client. You may receive a warning when importing the client code if
> your version of OpenSSL is too old or doesn't expose TLS v1.2.
>
> Significant changes that are not related to new Riak features:
>
> - Previously-marked deprecated methods/features have been removed. [5]
> - PB is now the default protocol for new clients. [6] HTTP is still
>   available, but this is part of our larger effort to phase out HTTP
>   in our official libraries.
>
> There are some significant known-issues with this package that you
> should be aware of:
>
> - Strongly-consistent keys will work (the API is similar enough to
>   regular K/V), but if a CAS update operation fails, your application
>   code will have to perform the retry. This will be wrapped in an API
>   for the final release.
> - We have had multiple reports of connections leaking while iterating
>   over streamed responses [7], these will be resolved by final
>   release.
> - Although the behavior hasn't changed, we will be attempting to
>   address a number of Unicode issues before final release [8].
>
> For all other known issues, please refer to the issue tracker on
> Github [9]. Milestones in the tracker refer to *Riak* releases
> although the client version is different. We encourage you to report
> any issues you find with the release candidate client.
>
> Cheers!
>
> [1] https://pypi.python.org/pypi/riak/2.1.0rc1
> [2] http://riak-python-client.readthedocs.org/en/master/
> [3] http://docs.basho.com/riak/2.0.0/dev/using/search/
>     http://docs.basho.com/riak/2.0.0/dev/advanced/bucket-types/
>     http://docs.basho.com/riak/2.0.0/dev/using/data-types/
>     http://docs.basho.com/riak/2.0.0/dev/data-modeling/data-types/
>     http://docs.basho.com/riak/2.0.0/ops/running/authz/
>     http://docs.basho.com/riak/2.0.0/dev/advanced/strong-consistency/
> [4] https://pypi.python.org/pypi/pyOpenSSL/0.14
> [5] https://github.com/basho/riak-python-client/pull/328
> [6] https://github.com/basho/riak-python-client/pull/341
> [7] https://github.com/basho/riak-python-client/issues/318
>     https://github.com/basho/riak-python-client/issues/312
> [8] https://github.com/basho/riak-python-client/issues/334
> [9] https://github.com/basho/riak-python-client/issues
>
> --
> Sean Cribbs <sean at basho.com <javascript:;>>
> Software Engineer
> Basho Technologies, Inc.
> http://basho.com/
>
> _______________________________________________
> riak-users mailing list
> riak-users at lists.basho.com <javascript:;>
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20140730/64bd3e4c/attachment.html>


More information about the riak-users mailing list