Aerospike Vector Search 0.9.0 Release Notes
July 9, 2024
Breaking Changes
- This version of AVS is not compatible with Python client 0.6.1 or earlier due to API name changes.
- The default metadata namespace has been changed from
proximus-meta
toavs-meta
. - Log and configuration filenames and locations have been updated to reflect the official product name.
- The prefix on all metrics has been changed to aerospike_vector_search.
- The top-level
aerospike
configuration stanza has been changed tostorage
.
New features
AVS now supports authentication for users. See Manage AVS users for more information. [VEC-158]
Added TLS support for network security. See TLS [VEC-159]
This release includes an index healing process in AVS. See Healer for more information. [VEC-149, VEC-19]
Added metrics for monitoring the index healing process. [VEC-21]
Improvements
AVS now returns an error when the cluster is not well-formed for index operations. [VEC-206]
If you try to create an index with a bin name that is greater than 15 characters, AVS throws an error. [VEC-192]
Updated the name of the queue size metric so that it is easier to identify and graph. [VEC-178]
Renamed Java client artifacts to use aerospike_vector_search instead of proximus. [VEC-173]
Renamed the Java clients VectorDbClient and VectorDbAdminClient to client and adminClient, respectively. [VEC-172]
Changed the name of artifacts, clients, configuration properties, and so on from Proximus to Aerospike Vector Search. [VEC-137]
When index data hits stop-writes, the index remains searchable but no longer handles ingestion, and an improved error message is logged. [VEC-160]
Supported Clients
This release supports the following AVS clients:
Known Issues
- You must include optional fields
hnsw-batch-interval
andhnsw-batch-max-records
when updating indexes, even if you want to use current or default values. - Healer cycles can significantly impact QPS performance.