Releases: aerospike/aerospike-client-nodejs
Releases · aerospike/aerospike-client-nodejs
v2.3.1 / 2016-08-11
- Bug Fixes
- Fix installation on Amazon Linux. #143
v2.3.0 / 2016-08-11
- New Features
- Add Client#infoAll method to simplify processing info responses from multiple hosts. #43
- Bug Fixes
- Improvements
- Improved C-client resolution to avoid issues fetching C client artifact during npm package installation
- Updates
- Update C client library to v4.0.7.
- Drop support for Debian 6
v2.2.0 / 2016-07-13
- Improvements
- Added back support for applying stream UDF to query results w/o aggregation.
- Added
maxConnsPerNode
config setting to address #130.
v2.1.1 / 2016-06-29
- Fixes
- Prevent segfault processing query/scan record stream if client object goes out of scope. [CLIENT-735]
- Update C client to v4.0.6 with fix to complete scan on empty sets. #132
v2.1.0 / 2016-06-03
- New Features
- Support for operations on Sorted Maps. Requires Aerospike server version 3.8.4 or later.
- Improvements
- Key objects returned in callbacks now include the digest
- Code cleanup to support [email protected] which adds several new rules
- Fixes
- Fix compile time error with Node 0.12 using gcc 4.4. #131
- Changes
- The
aerospike.operator
module has been split up into two seperate modulesaerospike.operations
andaerospike.lists
for operations on scalar and
list data types respectively. See detailed list of API changes
for further details.
- The
- Documentation
- Pulled client configuration out into a separate class and expanded the documentation.
- Documented
sharedMemory
configuration. - Added tutorial for using Aerospike client in Node.js cluster setup.
v2.0.4 / 2016-05-09
v2.0.3 / 2016-05-03
- Fixes
- Event loop does not get released if module gets required but never used to open & close client connection.
#124
- Event loop does not get released if module gets required but never used to open & close client connection.
v2.0.2 / 2016-04-29
v2.0.1 / 2016-04-27
- Improvements
- Optimize callback handler performance. #119
- Removed some unused async C++ helper functions; minor code cleanup
- Fixes
- Ensure callbacks are always called asynchronously, even for param errors
raised by the client itself. #120
- Ensure callbacks are always called asynchronously, even for param errors
- Tests
- Complete tests for writing bins with specific data types
- Extend query/scan performance tests
- Documentation
- Minor JSDoc documentation fixes
v2.0.0 / 2016-04-19
- Improvements
- Performance: Use asynchronous client commands of the new Aerospike C/C++ client library
version 4.0. - Follow Node.js error-first callback conventions: The client now returns
null
as the first parameter (error
) in most callbacks when the command
was executed successfully. See backward incompatible API changes for more details. #105,
PR #106. Thanks to @eljefedelrodeodeljefe! - Added support for pluggable callback handler logic for backwards
compatibility with legacy error callback semantics. - Added new
batchRead
command to support reading different
namespaces/bins for each key in a batch. This method requires Aerospike
server version >= 3.6.0. The batchGet/batchExists/batchSelect client
commands deprecated but still supported for backwards compatibility. - Added
isConnected
client method to check cluster connection status. #108 - Added support for creating secondary indexes on list and map values;
requires Aerospike server version >= 3.8. [CLIENT-684] - Added new filter predicates in the
Aerospike.filter
module:- contains() to match on list/map membership for integer & string values #74
- geoWithinRadius() to match on geospatial locations within a given radius
from another point (incl. geospatial locations in lists and maps) - geoContainsPoint() to match on geospatial regions that include given
lng/lat coordinates (incl. geospatial regions in lists and maps) - geoContains() is deprecated and has been replaced by
geoContainsGeoJSONPoint() - geoWithin() is deprecated and has been replaced by
geoWithinGeoJSONRegion()
- Added new Scan API implementation via
Client#scan
. - Added new Query API with support for query aggregation using Stream UDFs as well as background queries using Record UDFs #65
- Added new
Job
class to query status of long-running background tasks, including scans, queries and index creation. - Added new
Key
,Double
andGeoJSON
classes replacing existingaerospike.key()
,aerospike.Double()
andaerospike.GeoJSON()
functions. - Added
Aerospike.info
module withparseInfo
utility method to parse info
string returned by Aerospike cluster nodes usingClient#info
method. - Added missing status codes to
Aerospike.status
. - Added support for set compression threshold policy for write operations,
retry policy for read operations, and ttl policy for apply operations. - Improvements to the client's mocha test suite, incl. performance improvements by re-using a single client connection for all tests.
- Performance: Use asynchronous client commands of the new Aerospike C/C++ client library
- Fixes
- Fix possible memory corruption parsing UDF module or function names.
- Node segfaults when trying to query the aerospike client after closing the
connection. #88
- Changes
- Drop support for Node.js v0.10. The Aerospike Node.js client now requires
Node.js v0.12 or later. - Several client commands have been renamed and the old method names have been deprecated; please refer to the full list of backward incompatible changes for details.
- Drop support for Node.js v0.10. The Aerospike Node.js client now requires
- Documentation
- JSDoc-style annotations have been added throughout the library code and new
API documentation is generated from the source code using JSDoc v3. The generated API docs are hosted
at http://www.aerospike.com/apidocs/nodejs/.
- JSDoc-style annotations have been added throughout the library code and new