--- title: "Aerospike Database 6.1.0.1 Release Notes" description: "Release notes for Aerospike Database 6.1.0.1 covering new SINDEX features, CDT updates, and upgrade instructions." --- # Aerospike Database 6.1.0.1 Release Notes > For the complete documentation index see: [llms.txt](https://aerospike.com/docs/llms.txt) > > All documentation pages available in markdown. August 30, 2022  |  **[Download](https://aerospike.com/download/)** ## New in this version This version implements a variety of feature requests and improvements to enhance performance, usability and reliability. ### New features **Enterprise, Federal and Community editions** - (SINDEX) Secondary index names now have a 64-character limit (including a null terminator). - AER-6545 - (SINDEX) Added ability to define secondary indexes on elements within CDTs (Collection Data Types), by using CDT [`contexts`](https://aerospike.com/docs/database/tools/asadm/live-mode/#create-a-secondary-index). - Added list operation [`EXISTS`](https://aerospike.com/docs/develop/data-types/collections/list/operations#return-types) return type. - Added map operation [`EXISTS`](https://aerospike.com/docs/develop/data-types/collections/map/operations#return-types) return type. - Database 6.1.0 removes `num-partitions` and adds the [`sindex-stage-size`](https://aerospike.com/docs/database/reference/config#namespace__sindex-stage-size) configuration parameter for secondary indexes in the namespace context. `sindex-stage-size` is similar to the existing primary index [`index-stage-size`](https://aerospike.com/docs/database/reference/config#namespace__index-stage-size) configuration parameter. If the `sindex-stage-size` value is changed across a restart, any secondary indexes for the namespace will be rebuilt. - Database 6.1.0 includes a simple feature key file allowing only for a single-node cluster. The feature key will not be valid for versions after Database 6.1.0. - Be aware of your package manager’s handling of existing configuration files during installation. If the configuration file was updated, we keep the existing \*.deb or \*.rpm respective configuration file. It is the uninstallation of the package where these systems diverge. - Debian and Ubuntu (\*.deb) leaves the modified configurations in place. - Redhat (\*.rpm) renames the configuration file with an \*.rpmsave extension. **Enterprise and Federal editions only** - AER-6543 - (SINDEX) Added support for warm restart of secondary indexes. ### Updates - Attempting to create a secondary index which already exists now returns success/OK instead of an error. - You can create [`Map indexing`](https://aerospike.com/docs/develop/data-types/collections/map/index-and-query) and [`List indexing`](https://aerospike.com/docs/develop/data-types/collections/list/index-and-query) at any depth. For example, you can create an index on a map inside of a bin that is inside of another map. - Debian 9 [Stretch LTS](https://wiki.debian.org/LTS/Stretch) reached its End of Life on June 30 2022. Aerospike will drop support for Debian 9 in the Database 6.2.0 release. - See [Platform support and compatibility](https://aerospike.com/docs/database/reference/platform-support) for all currently supported platforms. - [Aerospike Tools 7.2.0](https://aerospike.com/docs/database/tools/release-notes/#tools-720) ### Improvements **Enterprise, Federal & Community** - AER-6530 - (BATCH) Added an option to ensure that a sub-transaction error that stops a response will be included in the response. - AER-6532 - (CDT) Added `EXISTS` return type, which may be used to optimize certain `GET` operations. - AER-6535 - (INFO) Added `sindex-name` field to `query-show` output. - AER-6548 - (INFO) Added `smd-show` command to retrieve raw SMD module data. - AER-6531 - (LOGGING) Added `long-queries` to `in-progress` ticker line, and renamed `queries_active` to `long_queries_active`. - AER-6537 - (QUERY) Partially de-duplicate responses to range queries on list or map secondary indexes. - AER-6546 - (SINDEX) When indexing list or map keys or values, iterate in msgpack directly instead of converting to as\_list or as\_map. - AER-6550 - (SINDEX) A secondary index without a set name now applies to the entire namespace. - AER-6551 - (SINDEX) The size limit for a secondary index name has been reduced to 64. - AER-6547 - (STATS) Added `entries_per_bval` and `entries_per_rec` secondary index cardinality statistics. - AER-6534 - (UDF) New as\_map implementation improves (de-)serialization of ordered maps when executing UDFs. **Enterprise & Federal Only** - AER-6549 - (DEPLOYMENT) Automatically install an Enterprise evaluation feature key. - AER-6538 - (SINDEX) For `index-type` flash namespaces, use smaller internal batch sizes for garbage collection and queries, to minimize time under lock. - AER-6540 - (STATS) Added `bytes_shipped` namespace statistic in XDR. - AER-6544 - (XDR) For connector destinations, use digest affinity (instead of round-robin) to ensure that a record always goes to the same node. - AER-6565 - (XDR) Distribute recovery/rewind requests across service threads using partition affinity, avoiding lock contention and significantly improving performance. ## Upgrade and downgrade instructions For full instructions on upgrading and downgrading, see [Upgrade or Repair Server](https://aerospike.com/docs/database/install/upgrade) and [Special upgrade instructions for Database 6.1.0](https://aerospike.com/docs/database/advanced/special-upgrades/610-upgrade). - Before you upgrade, find any secondary index names that exceed the new 64-character limit (including a null terminator), delete them, then recreate the sindex with a shorter name after the upgrade. - When upgrading, the secondary index [`sindex-create`](https://aerospike.com/docs/database/reference/info#sindex-create) applies to the entire namespace, if the set parameter is omitted. - [Downgrade from Aerospike Database 6.1.0 to 6.0.0](https://aerospike.com/docs/database/advanced/special-upgrades/610-to-600-downgrade). - If you have to downgrade from a deployment of Database 6.1.0 that has a secondary index stored in shared memory, delete the shared memory segments after stopping the server (asd), in order to reclaim this memory. - Downgrading from Database 6.1.0 forces a [cold start](https://aerospike.com/docs/database/manage/database/cold-start). ## Compatiblity - Use [Prometheus Exporter](https://aerospike.com/docs/database/observe/monitor/release/exporter) version 1.2.1 or later to run Prometheus Exporter with Aerospike Database 6.1.0. ## Known Issues - If you use `equality` secondary index queries that return a small number of records, you may see a latency increase in Database 6.0.0-6.2.0. The [`inline-short-queries`](https://aerospike.com/docs/database/reference/config#namespace__inline-short-queries) configuration option provides a partial fix in Database 6.3.0, and a more advanced fix is scheduled for Database 6.4.0. - If your secondary index query only returns 0 records or 1 record, meaning that it is acting as a unique index, you should consider converting such a query to a get/exists operation by creating a self-managed reverse index (lookup table). - Spark Connector version 3.5 starts using batch writes when possible, a feature which was introduced in Aerospike Database 6.0.0. Consult the Spark Connector [rate limiting documentation](https://aerospike.com/docs/connectors/spark/rate-limiting#set-rate-quotas-in-the-spark-application) before you upgrade the server. Pay attention to throttling write throughput, and use Spark Connector 3.5.5 or later, which fixes throttling behavior to conform to the `aerospike.transaction.rate`. - There is a possibility of partial de-duplicate (repeated records) in secondary index query (SI query) responses for SI queries that use list or map type secondary indexes. Any record that satisfies such a query at least once will be included, but it is possible and normal to see a record more than once. - [Known issues for 6.1.0.1](https://aerospike.com/docs/database/reference/issues?search=6.1.0.1)