Aerospike

Latest version: v15.0.0

Safety actively analyzes 629678 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 9 of 16

2.2.3

Fixes
- Ensures consistent setting of permission bits for pip distributions.

2.2.2

Fixes
- Add support for C client resolution when compiling on Amazon Linux.

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.

Page 9 of 16

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.