Releases: aerospike/aerospike-client-python
2.2.3
Fixes
- Ensures consistent setting of permission bits for pip distributions.
2.2.2
2.2.1
Changes
- Updated to C client version 4.1.8
- Allowed setting of the
max_socket_idle
for all connections instead of only being configurable for TLS connections. Parameter has been moved from the tls config dictionary to the main config dictionary. Although the previous syntax will not raise an exception, it will not set the value.
# Version 2.2.1:
config = {
'hosts': hostlist,
'max_socket_idle': 55
}
client = aerospike.client(config)
# Previous versions
config = {
'hosts': hostlist,
'tls': {'max_socket_idle': 55}
}
client = aerospike.client(config)
-
Improved the distribution of the client. Support files will be stored in the same location regardless of whether a binary or source wheel was the source.
-
Changed installation of system Lua files:
The default location of the Lua files needed for stream UDF aggregation was moved from: /usr/local/aerospike/lua
to the directory aerospike/lua
inside of the Python installation directory for storing system dependent packages. This directory can be found by running: Python -c "import sys; print(sys.exec_prefix);"
Or if the extension was installed via pip: pip show -f aerospike
By default the client will look for the system .lua files in /usr/local/aerospike/lua
we recommend either moving the files from aerospike/lua to that directory or specifying the path to those files in the client constructor.
If you did not specify an installation location, and Python -c "import sys; print(sys.exec_prefix);"
returned /home/user/.virtualenvs/aerospike-py
This means that the system lua files are located in: /home/user/.virtualenvs/aerospike-py/aerospike/lua/
and that is the directory which should be specified in the constructor.
So if installing the Python client for Aerospike stored the data files in /home/user/.virtualenvs/aerospike-py/aerospike/lua
lua_config = {"system_path": "/path/to/lua_dir", "user_path": "/path/to/usr-lua-dir"}
2.1.3
Fixes
- Setting use_batch_direct in get_many causes an error. CLIENT-909
- Memory corruption caused by long role names in admin methods. CLIENT-910
- Memory leak in client.info with unicode request strings. CLIENT-912
- Modify operate_ordered to perform operations in a single transaction.
- Update the SHM documentation.
- Update documentation for operate and operate_ordered
2.1.2
Features
- Improved compiled wheel compatibility with different versions of OS X.
- Expose batch policy config options (see documentation). CLIENT-907
2.1.1
Fixes
- Improved OS X compilation steps. CLIENT-791 CLIENT-904
- Update setup.py to lock the c client version correctly.
- Docs - Improved clarity of readme and build instruction files.
2.1.0
2.0.13
Fixes
- Fix issue when trying to register an empty or non-existent lua file. CLIENT-883 CLIENT-884
- Python 2.7 unicode bin names in select are not returned. CLIENT-485
- Memory corruption on operation_destroy. CLIENT-885
- Fix for null fields in exceptions.
- Fixes for two byte issues, change to always return bytearray for unsupported bytes type.
- Improved error messages for client constructor.
- Treat key as bytes if unicode decoding fails. (Thanks @mluscon!)
New Behavior
- Previous versions of Python client would attempt to share the aerospike object automatically. If this behavior is desired, you now must enable sharing via the use_shared_connection parameter. See docs.
2.0.12
Fixes
- Add in missing error codes so the client errors will match what is coming back from the server.
- Fix build on Alpine Linux (thanks @OndraVoves!)
2.0.11
Features
- Support configurable scan socket write timeout for python. CLIENT-872
- Support truncate api for python. CLIENT-855
Fixes
- Update to c-client version 4.1.5.
- Stream UDFs - python udf_put() does not update client side udf. CLIENT-820
- Query Segfaults when a record contains a Python Blob bin which can not be deserialized. CLIENT-880
- Calling Map Size on a non existent bin returns a very large number. CLIENT-843