Aerospike agent changelog
Release notes
2.3.1.3
Released: October 29, 2026
-
Target: a page is written on ordered lanes bounded by the
writerssetting, which until now changed nothing on this target, so two writes of the same record never overtake each other;
2.3.1.0
Released: October 25, 2026
-
Target: write chunks are sized by the payload of the rows;
-
Date, time, date-time and offset date-time columns map to Aerospike’s own date and time types when an entity is created. Before, the source’s own type name was used, which Aerospike could refuse when the entity was saved;
2.3.0.4
Released: October 23, 2026
-
TLS connections open again. With TLS on, the client recognises its event loop group by probing the epoll, kqueue and io_uring Netty transports, and a missing class ended in "Unexpected EventLoopGroup", so no TLS connection could be built. Those transport classes now ship with the agent;
2.3.0.3
Released: October 21, 2026
-
With Use batch writes (
useBatchWrites) on, each key of a batch is written with only the bins of its own row. Before, the bins of every row in a write chunk went to every key in it, so records ended up with another row’s values. Rows of one chunk that share a key are merged in chunk order, the later row winning per bin, as the sequential path leaves them. A record the server rejects in a batch now fails the write instead of being dropped;