- 1.0: Initial implementation
- 1.1: Insert system time along with the record.
- Added Json datatype support (List, Maps can be nested also.)
- Added TLS security support
- Added mapping section. user can mention any number of mappings in one file. User can add secondary_mapping (used for any column to primary key mapping.) by adding attribute secondary_mapping: 'true'.
- Added (-g) (max-throughput) to limit max average throughput of loader.
- Removed Specific List/Map datatype option as supported type. Json datatype will cover them.
- Removed CSV specific options from config file. There will be only DSV support (covers CSV also.)
- Changed parameter options to be consistent with Aerospike-java-client parameters.
- Added simple examples explaing all datatype and config options simply.
- Deprecated -s (--set) commandline param. Will be passed only by config file.
- Deprecated -wt (write-threads), -rt (read-threads) and introduce new option -g defining max throughput for loader.
- Changed schema for mapping definitions.
- None
- Fixed config-name binlist in docs. Changed to bin_list
- Added native float support. Earlier float was stored as blob.
- Fixed loading for JSON object. Now JSON object format in datafile will be of Standerd JSON. limitation (JSON specific special char ('[', '{', ',', ':') can't be used as delimiter.)
- Fixed tests.
- Fix docs related to json spec.
- Fix examples for JSON object.
- Added GeoJson support.
- Fixed data upload counters.
- Fix docs related to json/geojson spec.
- Fix examples for GeoJSON object.
- Add shebang to run_loader script to allow execution from non-bash based shells.
- Update log4j to version 2.15.0.
- Update log4j to version 2.16.0.
- Update log4j to version 2.17.1.
- TOOLS-2346 Upgrade Java client to 6.1.6.
- Aerospike Java client to 6.1.6 is only compatible with Aerospike server versions 4.9 or newer.
- TOOLS-2322 Write key ordered maps by default.
- TOOLS-2347 Add -um, --unorderedMaps flags.
- Forces all maps to be written as unorderd maps. This was standard before the 3.0.0 asloader release.
- TOOLS-2469 (ASLOADER) Float data type loses precision, change to double.
- Asloader 4.0.0 will parse data specified as "float" in the JSON spec as Java doubles. This means you may see changes in the precision of floating point values when compared to previous versions of asloader. Parsing as double matches the precision of the Aerospike double data type which is what all floats are stored as in the Aerospike database.
- TOOLS-1669 Handle CVE-2020-9488 in asloader.
- TOOLS-1670 Handle CVE-2020-15250 in asloader.
- TOOLS-2469 (ASLOADER) Float data type loses precision, change to double.
- [Snyk] Upgrade com.aerospike:aerospike-client from 6.1.6 to 6.1.7 by @snyk-bot
- [DOCS-1320] [Snyk] Upgrade org.apache.logging.log4j:log4j-core from 2.17.1 to 2.19.0 by @snyk-bot
- [DOCS-1320] [Snyk] Upgrade commons-cli:commons-cli from 1.2 to 1.5.0 by @snyk-bot
- [TOOLS-1670] [TOOLS-1690] Bump junit from 4.11 to 4.13.1 by @dependabot
- [Snyk] Security upgrade com.aerospike:aerospike-client from 6.1.7 to 7.0.0 by @arrowplum in #40
- TOOLS-2640 fix CVE-2023
- [Snyk] Upgrade org.apache.logging.log4j:log4j-api from 2.20.0 to 2.21.0
- [Snyk] Upgrade org.apache.logging.log4j:log4j-core from 2.20.0 to 2.21.0
- [Snyk] Upgrade commons-cli:commons-cli from 1.5.0 to 1.6.0
- TOOLS-2826 (ASLOADER) Fixed an issue where ldap users fail read-write role validation. Asloader no longer checks if the Aerospike user has read-write permissions before beginning writes.
- [Snyk] fix: upgrade org.apache.logging.log4j:log4j-core from 2.21.0 to 2.22.1
- [Snyk] fix: upgrade org.apache.logging.log4j:log4j-api from 2.21.0 to 2.22.1
- [Snyk] fix: upgrade org.apache.logging.log4j:log4j-api from 2.21.0 to 2.22.1
- [TOOLS-2690] (ASLOADER) Set client policy maxConnsPerNode to the max amount of worker threads to prevent out of connection errors.