Releases: aerospike/aerospike-client-go
Minor feature and bug fix release.
Minor fix release.
-
Fixes
- [CLIENT-1204] Retry logic will keep retrying on
KEY_NOT_FOUND
errors untilpolicy.MaxRetries
is hit or record is returned to the client.
- [CLIENT-1204] Retry logic will keep retrying on
Minor improvements and bug fix release.
-
Improvements
- Improves testing for float64 precision formatting between amd64 and aarch64.
-
Fixes
- [CLIENT-2019] Write Batch operation with an invalid namespace record causes all batch transactions to fail.
- [CLIENT-2020] Support
QueryPartitions
with non-nil filter (secondary index query)
Minor improvements and bug fix release.
-
Improvements
- [CLIENT-1959] Retry a foreground scan/query partition to a different replica when a partition unavailable error occurs.
- [CLIENT-1957] Handle
Query
,QueryExecute
andQueryAggregate
on non-existing sets without timing out. - [CLIENT-1956] Return an error when a read operation is used in a background query.
-
Fixes
- [CLIENT-1958] Prevent division by zero if the node array is empty in
Cluster.GetRandomNode()
. - [CLIENT-1955] Allow
BatchPolicy.SendKey
to be applied to all batch keys in all batch commands. Batch commands used inBatchOperate
take an independent policy object. We used to ignore theSendKey
attribute in those policies.
- [CLIENT-1958] Prevent division by zero if the node array is empty in
Minor feature and bug fix release.
-
New Features
- [CLIENT-1852] Add
ListSetWithPolicyOp
to list operations.
- [CLIENT-1852] Add
-
Fixes
- [CLIENT-1852] Fix
ListRemoveByIndexRangeOp
index param type. - [CLIENT-1855] Fix an issue where
ListGetByValueRangeOp
,ListRemoveByValueRangeOp
withnil
end value return empty slice. - [CLIENT-1867] Fix an issue where
BatchOperate
returns unexpectedResultCode
for successful records when a record within a batch returns an error.
- [CLIENT-1852] Fix
Major fix release
This is a Major fix release. We recommend you update to this version ASAP. A bug might occur when a client performing a scan hits a "Partition Unavailable" during an unstable cluster (in both high availability (AP) and strong consistency (CP) modes). Previous versions of the client aborted the scan and put the connection back into the pool, which might cause unprocessed results to be sent to a different transaction (of the same client), possibly resulting in incorrect application behavior. This has been fixed by Go Client v5.10.0 and v6.4.0.
-
Fixes
- [CLIENT-1827]
IdleTimeout
new default 0 may be missing tend thread reaping. - [CLIENT-1822] Scan/Query/Other streaming commands, including some Batch could put a faulty connection back to the pool after a cluster event where in certain conditions its buffer contents would end up in another scan and mix the results.
- Update go.mod, redact buggy versions and update required Go version to v1.16
- [CLIENT-1827]
-
Improvements
- Update the examples for the new scan/queries
- Avoid indirection for
[]byte
conversion during reflection. Resolves #382. - Change v5 to v6 in some outdated documentation.
Major fix release
This is a Major fix release. We recommend you update to this version ASAP. A bug might occur when a client performing a scan hits a "Partition Unavailable" during an unstable cluster (in both high availability (AP) and strong consistency (CP) modes). Previous versions of the client aborted the scan and put the connection back into the pool, which might cause unprocessed results to be sent to a different transaction (of the same client), possibly resulting in incorrect application behavior. This has been fixed by Go Client v5.10.0 and v6.4.0.
-
Fixes
- [CLIENT-1822] Scan/Query/Other streaming commands, including some Batch could put a faulty connection back to the pool after a cluster event where in certain conditions its buffer contents would end up in another scan and mix the results.
- Update go.mod, redact buggy versions and update required Go version to v1.16
- Fixes a few test errors for server v6.1+.
- Adds a
nil
check for error in the execution retry.
-
Improvements
- Update the examples for the new scan/queries.
- Avoid indirection for
[]byte
conversion during reflection. Resolves #382.
Minor feature release
-
New Features
- [CLIENT-1802] Support creating a secondary index on elements within a CDT using context. Supported by server v6.1+.
- [CLIENT-1773] Change client configuration defaults:
- Set
ClientPolicy.ConnectionQueueSize
from 256 to 100. - Set
ClientPolicy.IdleTimeout
from 55 to 0 secs. - Set
ClientPolicy.MaxErrorRate
from 0 to 100. - Set
Policy.TotalTimeout from
0 to 1000ms for all commands except scan/query.
- Set
-
Fixes
- Fixed a few Linter warnings.
-
Improvements
- Documented a few constraints in HLL API docs.
- Documented that PartitionFilter is both a filter and a cursor in the API docs.
Hotfix Release
This is mostly a re-release of v6.2.0, with one added minor change. It seems that we bungled the Github tag somehow for that release. Upgrade from v6.2.0 to this version for the changes in that version to be applied to your code.
- Fixes
- Add a nil check for error in batch retry to be on the safe side.
Major fix release
NOTE: It seems that the tag reference for this release was incorrect on Github, or we somehow confused the Go mod
. Do not use this version. Use v6.2.1 instead.
This is a major fix release. We recommend upgrading to this release if you are using BatchOperate
or Scan/Queries
.
-
Fixes
- [CLIENT-1783] Client crashes when tracker is
nil
during Scan/Queries. - [CLIENT-1782]
BatchOperate
doesn't return errorBATCH_MAX_REQUESTS_EXCEEDED
. - [CLIENT-1781] Fix
BatchOperate
: use offset index to pick correct record.
- [CLIENT-1783] Client crashes when tracker is
Re-release to resolve github tag mixup
This is only a retag of v5.9.0, since that release bungled up tagging properly and causes issues with go.mod according to #386