Releases: oracle/coherence-go-client
Coherence Go Client - v2.3.0-rc2
Introduction
This is release v2.3.0-rc2 of the Coherence Go Client, an API for accessing Coherence via a native Go client.
Requirements
- Coherence CE 22.06.4+, 14.1.2+, 24.03+, or Coherence 14.1.1.2206.4+, 14.1.2.0 Commercial edition with a configured gRPCProxy. (Always ensure you are using the latest Coherence available patch.)
- Go 1.23.+
NOTE: Due to CVE's in core Go packages (golang.org/x/net in particular), the minimum Go version for v2.1.0+ is now 1.23. If you wish to use a go version < 1.12, you can use V2.0.0 of the client.
go get github.com/oracle/coherence-go-client/[email protected]
Updates / New Features - v2.3.0-rc2
- Add the
EntrySetFilterWithComparator
function which allows sorting of results using a comparator, when retrieving entry set when using a filter - Added the
extractors.Comparator
interface andextractors.ExtractorComparator
function to support the above. - Example:
age := extractors.Extract[int]("age") fmt.Println("Retrieve the people between the age of 17 and 21 and order by age ascending") ch := coherence.EntrySetFilterWithComparator(ctx, namedMap, filters.Between(age, 17, 21), extractors.ExtractorComparator(age, true)) for result := range ch { if result.Err != nil { panic(result.Err) } fmt.Printf("Key: %v, Value: %s\n", result.Key, result.Value.String()) }
Note: This feature is only available when connecting to Coherence server versions CE 25.03+ and commercial 14.1.2.0+.
Note: the entries are sorted internally on the gRPC proxy to avoid excessive memory usage, but you need to be careful
when running this operation against NamedCaches with large number of entries.
Examples
- Added a new example to show using a custom
Comparator
and customEntryProcessor
. See Go client examples for more information
Bug Fixes
- Harden the reconenction logic when retrieving streamed data via various EntrySet*, Values* and Keys* operations
Upgrading from v1.2.2
If you were previously using v1.2.2 then you will need to update your import statements to specify:
"github.com/oracle/coherence-go-client/v2/coherence"
instead of
"github.com/oracle/coherence-go-client/coherence"
Breaking Changes
- N/A
What's Changed - rc2
- Update various deps by @tmiddlet2666 in #126
- Initial EntrySetFilterWithComparator by @tmiddlet2666 in #127
- Increase retries and display http status code for curl by @tmiddlet2666 in #128
- Add additional test and clarification for channels doc by @tmiddlet2666 in #130
- Add additional kind tests by @tmiddlet2666 in #131
Full Changelog: v2.2.0...v2.3.0-rc2
Coherence Go Client - v2.3.0-rc1
Introduction
This is release v2.3.0-rc1 of the Coherence Go Client, an API for accessing Coherence via a native Go client.
Requirements
- Coherence CE 22.06.4+, 14.1.2+, 24.03+, or Coherence 14.1.1.2206.4+, 14.1.2.0 Commercial edition with a configured gRPCProxy. (Always ensure you are using the latest Coherence available patch.)
- Go 1.23.+
NOTE: Due to CVE's in core Go packages (golang.org/x/net in particular), the minimum Go version for v2.1.0+ is now 1.23. If you wish to use a go version < 1.12, you can use V2.0.0 of the client.
go get github.com/oracle/coherence-go-client/[email protected]
Updates / New Features - v2.3.0-rc1
- Add the
EntrySetFilterWithComparator
function which allows sorting of results using a comparator, when retrieving entry set when using a filter - Added the
extractors.Comparator
interface andextractors.ExtractorComparator
function to support the above. - Example:
age := extractors.Extract[int]("age") fmt.Println("Retrieve the people between the age of 17 and 21 and order by age ascending") ch := coherence.EntrySetFilterWithComparator(ctx, namedMap, filters.Between(age, 17, 21), extractors.ExtractorComparator(age, true)) for result := range ch { if result.Err != nil { panic(result.Err) } fmt.Printf("Key: %v, Value: %s\n", result.Key, result.Value.String()) }
Note: This feature is only available when connecting to Coherence server versions CE 25.03+ and commercial 14.1.2.0+.
Note: the entries are sorted internally on the gRPC proxy to avoid excessive memory usage, but you need to be careful
when running this operation against NamedCaches with large number of entries.
Examples
- Added a new example to show using a custom
Comparator
and customEntryProcessor
. See Go client examples for more information
Bug Fixes
- N/A
Upgrading from v1.2.2
If you were previously using v1.2.2 then you will need to update your import statements to specify:
"github.com/oracle/coherence-go-client/v2/coherence"
instead of
"github.com/oracle/coherence-go-client/coherence"
Breaking Changes
- N/A
What's Changed
- Update various deps by @tmiddlet2666 in #126
- Initial EntrySetFilterWithComparator by @tmiddlet2666 in #127
- Increase retries and display http status code for curl by @tmiddlet2666 in #128
Full Changelog: v2.2.0...v2.3.0-rc1
Coherence Go Client - v2.2.0
Introduction
This is release v2.2.0 of the Coherence Go Client, an API for accessing Coherence via a native Go client.
Requirements
- Coherence CE 22.06.4+, 14.1.2+, 24.03+, or Coherence 14.1.1.2206.4+, 14.1.2.0 Commercial edition with a configured gRPCProxy. (Always ensure you are using the latest Coherence available patch.)
- Go 1.23.+
NOTE: Due to CVE's in core Go packages (golang.org/x/net in particular), the minimum Go version for v2.1.0+ is now 1.23.
If you wish to use a go version < 1.12, you can use V2.0.0 of the client.
Updates / New Features
- Improve the way the Go client logs messages. (thanks to @mdelapenya for his suggestion in #123
- You can now configure the logging level via the
COHERENCE_LOG_LEVEL
environment variable. The default logging level isINFO
which will show connection information on startup. You can set toERROR
which will only show any error messages and minimize the output. Available log levels in increasing verbosity are:- ERROR
- WARNING
- INFO
- DEBUG
- ALL
- Note: Setting the log level to
ALL
will generate large numbers of detailed messages and should only be used for specialized debugging
- You can now configure the logging level via the
- Added support and CI/CD tests for latest CE and commercial patches
Bug Fixes
- N/A
Upgrading from v1.2.2
If you were previously using v1.2.2 then you will need to update your import statements to specify:
"github.com/oracle/coherence-go-client/v2/coherence"
instead of
"github.com/oracle/coherence-go-client/coherence"
Breaking Changes
- N/A
What's Changed
- Add 25.03 to CI/CD by @tmiddlet2666 in #118
- Bump golang.org/x/net by @tmiddlet2666 in #119
- Initial perf tests by @tmiddlet2666 in #120
- Add streaming tests by @tmiddlet2666 in #121
- Minor test updates by @tmiddlet2666 in #122
- Improve the way the Go client logs messages by @tmiddlet2666 (thanks to @mdelapenya) (https://github.com/mdelapenya)) in #125
Full Changelog: v2.1.0...v2.2.0
Coherence Go Client - v2.1.0
Introduction
This is release v2.1.0 of the Coherence Go Client, an API for accessing Coherence via a native Go client.
Requirements
- Coherence CE 22.06.4+, 14.1.2+, 24.03+, or Coherence 14.1.1.2206.4+, 14.1.2.0 Commercial edition with a configured gRPCProxy. (Always ensure you are using the latest Coherence available patch.)
- Go 1.23.+
NOTE: Due to CVE's in core Go packages (golang.org/x/net in particular), the minimum Go version this release is now 1.23.
If you wish to use a go version < 1.12, you can use V2.0.0 of the client.
Updates / New Features
- Added an explain/ trace example
- Added support for latest CE and commercial patches and release
- Updated to require Go 1.23 as a minimum
- Updated various dependencies to address various Go CVE's
- Added Go 1.24 to CI/CD
Bug Fixes
- Fix failing index test
Upgrading from v1.2.2
If you were previously using v1.2.2 then you will need to update your import statements to specify:
"github.com/oracle/coherence-go-client/v2/coherence"
instead of
"github.com/oracle/coherence-go-client/coherence"
Breaking Changes
- N/A
What's Changed
- Update README and examples for next release by @tmiddlet2666 in #107
- Update CE version in examples by @tmiddlet2666 in #108
- Make documentation link standard by @tmiddlet2666 in #109
- Update with latest CE releases by @tmiddlet2666 in #110
- Update CI/CD with correct snapshots by @tmiddlet2666 in #111
- Update docker images by @tmiddlet2666 in #112
- Add Go 1.24 to CI/CD by @tmiddlet2666 in #113
- Add explain/trace example by @tmiddlet2666 in #114
- Fix failing index test by @tmiddlet2666 in #116
- Update to require go 1.23 for v2.1.0 by @tmiddlet2666 in #117
Full Changelog: v2.0.0...v2.1.0
Coherence Go Client - v2.0.0
Introduction
This is release v2.0.0 of the Coherence Go Client, an API for accessing Coherence via a native Go client.
Requirements
- Coherence CE 22.06.4+, 14.1.2+, 24.03+, or Coherence 14.1.1.2206.4+, 14.1.2.0 Commercial edition with a configured gRPCProxy. (Always ensure you are using the latest Coherence available patch.)
- Go 1.19.+
Updates / New Features
- Added support for new internal gRPC v1 API in CE 24.09, CE 14.1.2 and commercial 14.1.2 and above. No changes are required in code, the Go client will automatically detect the new version and is backwardly compatible with existing supported versions . This version hardens event processing and adds support for proper implementation queues and other future protocols
- Added the ability to specify a pruneFactor (defaults to 0.8 or 80%) for a near cache. This indicates the percentage of the total number of units that will remain after the cache manager prunes the near cache(i.e. this is the "low watermark" value)
- The minimum TTL for near cache is now 1/4 second. This change was made to bring the client into parity with other clients and to improve the performance of the expiry operation in a near cache. You will received an error if you try to set the TTL < 1/4 second
- Updated Queue API - This update provides a more stable API and adds support for the following queue types
Queue
- a simple queue which stores data in a single partition and is limited to approx 2GB of storagePagedQueue
- a queue which distributes data over the cluster and is only limited by the cluster capacityDequeue
- a simple double-ended queue that stores data in a single partition
- Harden the connection check and resolver lookup on connection failover
Note: The queue API has changed and you will need to update your code. See breaking changes below.
Upgrading from v1.2.2
If you were previously using v1.2.2 then you will need to update your import statements to specify:
"github.com/oracle/coherence-go-client/v2/coherence"
instead of
"github.com/oracle/coherence-go-client/coherence"
Breaking Changes
Queues
- In this release, the queues API has been rewritten based upon the above internal gRPC v1 API. This was done to improve reliability, and prepare for support for other protocols in the future and Queues were affected. This means that Queues in v2.0.0+ of the coherence-go-client it will only work against CE 24.09+ or Commercial 14.1.2.0+ Coherence versions
- If you wish to use the old queue API <v2.0.0 , it will only work against Coherence CE 24.03
Other Breaking Changes
To ensure compatibility with other Coherence API's, the following functions now return channels of StreamedEntry[K, R]
rather than StreamedValue[R]
. You will need to change any code that uses the following API's:
InvokeAllFilter[K comparable, V any, R any]
- now returns<-chan *StreamedEntry[K, R]
InvokeAllKeys[K comparable, V any, R any]
- now returns<-chan *StreamedEntry[K, R]
Bug Fixes
- Fixed an issue where the resolve would not resolve addresses correctly on failover
Documentation
Getting Started
go get github.com/oracle/coherence-go-client/[email protected]
What's Changed
- Update jib version by @tmiddlet2666 in #94
- Add latest CE patches to workflow by @tmiddlet2666 in #95
- Add support for v1 of API by @tmiddlet2666 in #96
- Initial queues gRPCv1 support by @tmiddlet2666 in #97
- Update near cache to support synchronous listeners by @tmiddlet2666 in #98
- Update to use /v2 Module by @tmiddlet2666 in #99
- Minor doc update, near cache calc update by @tmiddlet2666 in #100
- Correct local cache size calculation and add tests by @tmiddlet2666 in #101
- Near cache expiry improvements by @tmiddlet2666 in #102
- Further near cache expiry optimizations by @tmiddlet2666 in #103
- Ensure Pruning when using high units memory prunes to the memory, not… by @tmiddlet2666 in #104
- Update version of x/net to v0.33.0 by @tmiddlet2666 in #105
- Add 14.1.2 to ci/cd by @tmiddlet2666 in #106
Full Changelog: v1.2.2...v2.0.0
Coherence Go Client - v2.0.0-rc3
Introduction
This is release v2.0.0-rc3 of the Coherence Go Client, an API for accessing Coherence via a native Go client.
Note: this is a release candidate only and functionality may be changes before the official
v2.0.0
release.
Requirements
- Coherence CE 22.06.4+, 24.03+, or Coherence 14.1.1.2206.4+ Commercial edition with a configured gRPCProxy. (Always ensure you are using the latest Coherence available patch.)
- Go 1.19.+
Updates / New Features
Since v2.0.0-rc2
- Optimize the near cache expiry logic. This change means the minimum time to set TTL for is 1/4 second to be on parity with other clients
Other Update
- Added support for new internal gRPC v1 API in CE 24.09 and commercial 14.1.2 and above. No changes are required in code, the Go client will automatically detect the new version and is backwardly compatible with existing supported versions . This version hardens event processing and adds support for proper implementation queues and other future protocols
- Added the ability to specify a pruneFactor (defaults to 0.8 or 80%) for a near cache. This indicates the percentage of the total number of units that will remain after the cache manager prunes the near cache(i.e. this is the "low watermark" value)
- The minimum TTL for near cache is now 1/4 second. This change was made to bring the client into parity with other clients and ti improve the performance of the expiry operation in a near cache. You will received an error if you try to set the TTL < 1/4 second
- Updated Queue API - This update provides a more stable API and adds support for the following queue types
Queue
- a simple queue which stores data in a single partition and is limited to approx 2GB of storagePagedQueue
- a queue which distributes data over the cluster and is only limited by the cluster capacityDequeue
- a simple double-ended queue that stores data in a single partition
- Harden the connection check and resolver lookup on connection failover
Note: The queue API has changed and you will need to update your code. See breaking changes below.
Breaking Changes
Queues
- In this release, the queues API has been rewritten based upon the above internal gRPC v1 API. This was done to improve reliability, and prepare for support for other protocols in the future and Queues were affected. This means that Queues in v2.0.0+ of the coherence-go-client it will only work against CE 24.09+ or Commercial 14.1.2.0+ Coherence versions
- If you wish to use the old queue API <v2.0.0 , it will only work against Coherence CE 24.03
Other Breaking Changes
To ensure compatibility with other Coherence API's, the following functions now return channels of StreamedEntry[K, R]
rather than StreamedValue[R]
. You will need to change any code that uses the following API's:
InvokeAllFilter[K comparable, V any, R any]
- now returns<-chan *StreamedEntry[K, R]
InvokeAllKeys[K comparable, V any, R any]
- now returns<-chan *StreamedEntry[K, R]
Bug Fixes
- Fixed an issue where the resolve would not resolve addresses correctly on failover
Documentation
Getting Started
go get github.com/oracle/coherence-go-client/[email protected]
What's Changed
- Update jib version by @tmiddlet2666 in #94
- Add latest CE patches to workflow by @tmiddlet2666 in #95
- Add support for v1 of API by @tmiddlet2666 in #96
- Initial queues gRPCv1 support by @tmiddlet2666 in #97
- Update near cache to support synchronous listeners by @tmiddlet2666 in #98
- Correct local cache size calculation and add tests by @tmiddlet2666 in #101
- Near cache expiry improvements by @tmiddlet2666 in #102
- Further near cache expiry optimizations by @tmiddlet2666 in #103
Full Change log: v1.2.2...v2.0.0-rc3
Coherence Go Client - v2.0.0-rc2
Introduction
This is release v2.0.0-rc2 of the Coherence Go Client, an API for accessing Coherence via a native Go client.
Note: this is a release candidate only and functionality may be changes before the official
v2.0.0
release.
Requirements
- Coherence CE 22.06.4+, 24.03+, or Coherence 14.1.1.2206.4+ Commercial edition with a configured gRPCProxy. (Always ensure you are using the latest Coherence available patch.)
- Go 1.19.+
Updates / New Features
Since v2.0.0-rc1
- Attempt to harden the connection check and resolver lookup on connection failover.
Other Update
- Added support for new internal gRPC v1 API in CE 24.09 and commercial 14.1.2 and above. No changes are required in code, the Go client will automatically detect the new version and is backwardly compatible with existing supported versions . This version hardens event processing and adds support for proper implementation queues and other future protocols.
- Added the ability to specify a pruneFactor (defaults to 0.8 or 80%) for a near cache. This indicates the percentage of the total number of units that will remain after the cache manager prunes the near cache(i.e. this is the "low watermark" value)
- The minimum TTL for near cache is now 1/4 second. This change was made to bring the client into parity with other clients and ti improve the performance of the expiry operation in a near cache. You will received an error if you try to set the TTL < 1/4 second
- Updated Queue API - This update provides a more stable API and adds support for the following queue types
Queue
- a simple queue which stores data in a single partition and is limited to approx 2GB of storage.PagedQueue
- a queue which distributes data over the cluster and is only limited by the cluster capacity.Dequeue
- a simple double-ended queue that stores data in a single partition
Note: The queue API has changed and you will need to update your code. See breaking changes below.
Breaking Changes
Queues
- In this release, the queues API has been rewritten based upon the above internal gRPC v1 API. This was done to improve reliability, and prepare for support for other protocols in the future and Queues were affected. This means that Queues in v2.0.0+ of the coherence-go-client it will only work against CE 24.09+ or Commercial 14.1.2.0+ Coherence versions
- If you wish to use the old queue API <v2.0.0 , it will only work against Coherence CE 24.03
Other Breaking Changes
To ensure compatibility with other Coherence API's, the following functions now return channels of StreamedEntry[K, R]
rather than StreamedValue[R]
. You will need to change any code that uses the following API's:
InvokeAllFilter[K comparable, V any, R any]
- now returns<-chan *StreamedEntry[K, R]
InvokeAllKeys[K comparable, V any, R any]
- now returns<-chan *StreamedEntry[K, R]
Bug Fixes
- Fixed an issue where the resolve would not resolve addresses correctly on failover
Documentation
Getting Started
go get github.com/oracle/coherence-go-client/[email protected]
What's Changed
- Update jib version by @tmiddlet2666 in #94
- Add latest CE patches to workflow by @tmiddlet2666 in #95
- Add support for v1 of API by @tmiddlet2666 in #96
- Initial queues gRPCv1 support by @tmiddlet2666 in #97
- Update near cache to support synchronous listeners by @tmiddlet2666 in #98
Full Change log: v1.2.2...v2.0.0-rc2
Coherence Go Client - v2.0.0-rc1
Introduction
This is release v2.0.0-rc1 of the Coherence Go Client, an API for accessing Coherence via a native Go client.
Note: this is a release candidate only and functionality may be changes before the official
v2.0.0
release.
Requirements
- Coherence CE 22.06.4+, 24.03+, or Coherence 14.1.1.2206.4+ Commercial edition with a configured gRPCProxy. (Always ensure you are using the latest Coherence available patch.)
- Go 1.19.+
Updates / New Features
- Added support for new internal gRPC v1 API in CE 24.09 and commercial 14.1.2 and above. No changes are required in code, the Go client will automatically detect the new version and is backwardly compatible with existing supported versions . This version hardens event processing and adds support for proper implementation queues and other future protocols.
- Added the ability to specify a pruneFactor (defaults to 0.8 or 80%) for a near cache. This indicates the percentage of the total number of units that will remain after the cache manager prunes the near cache(i.e. this is the "low watermark" value)
- Updated Queue API - This update provides a more stable API and adds support for the following queue types
Queue
- a simple queue which stores data in a single partition and is limited to approx 2GB of storage.PagedQueue
- a queue which distributes data over the cluster and is only limited by the cluster capacity.Dequeue
- a simple double-ended queue that stores data in a single partition
Note: The queue API has changed and you will need to update your code. See breaking changes below.
Breaking Changes
Queues
- In this release, the queues API has been rewritten based upon the above internal gRPC v1 API. This was done to improve reliability, and prepare for support for other protocols in the future and Queues were affected. This means that Queues in v2.0.0+ of the coherence-go-client it will only work against CE 24.09+ or Commercial 14.1.2.0+ Coherence versions
- If you wish to use the old queue API <v2.0.0 , it will only work against Coherence CE 24.03
Other Breaking Changes
To ensure compatibility with other Coherence API's, the following functions now return channels of StreamedEntry[K, R]
rather than StreamedValue[R]
. You will need to change any code that uses the following API's:
InvokeAllFilter[K comparable, V any, R any]
- now returns<-chan *StreamedEntry[K, R]
InvokeAllKeys[K comparable, V any, R any]
- now returns<-chan *StreamedEntry[K, R]
Bug Fixes
- Fixed an issue where the resolve would not resolve addresses correctly on failover
Documentation
Getting Started
go get github.com/oracle/coherence-go-client/[email protected]
What's Changed
- Update jib version by @tmiddlet2666 in #94
- Add latest CE patches to workflow by @tmiddlet2666 in #95
- Add support for v1 of API by @tmiddlet2666 in #96
- Initial queues gRPCv1 support by @tmiddlet2666 in #97
- Update near cache to support synchronous listeners by @tmiddlet2666 in #98
Full Change log: v1.2.2...v2.0.0-rc1
Coherence Go Client - v1.2.2
Introduction
This is release v1.2.2 of the Coherence Go Client, an API for accessing Coherence via a native Go client.
Requirements
- Coherence CE 22.06.4+, 24.03+, or Coherence 14.1.1.2206.4+ Commercial edition with a configured gRPCProxy.
(Always ensure you are using the latest Coherence available patch.) - Go 1.19.+
Updates
- Updated the gRPC resolver address
coherence:///host:port
to randomize the addresses that it returns. This can be turned off by setting the environment variableCOHERENCE_RESOLVER_RANDOMIZE=false
Bug Fixes
- N/A
Documentation
Getting Started
go get github.com/oracle/coherence-go-client@latest
After executing this command coherence-go-client is ready to use, and it's source will be in:
$GOPATH/pkg/mod/github.com/oracle/coherence-go-client@latest
What's Changed
- Prepare for next release by @tmiddlet2666 in #91
- Add environment vairable to randomize resolver addresses by @tmiddlet2666 in #92
- Minor doc update by @tmiddlet2666 in #93
Full Changelog: v1.2.1...v1.2.2
Coherence Go Client - v1.2.1
Introduction
This is release v1.2.1 of the Coherence Go Client, an API for accessing Coherence via a native Go client.
Requirements
- Coherence CE 22.06.4+, 24.03+, or Coherence 14.1.1.2206.4+ Commercial edition with a configured gRPCProxy.
(Always ensure you are using the latest Coherence available patch.) - Go 1.19.+
Major New Features
- Added support to use the Coherence Name Service to lookup gRPC endpoints by specifying the resolve address of
coherence:///host:port
where host is a machine in the cluster and port is the cluster port.
E.g.coherence:///localhost:7574
Bug Fixes
- N/A
Documentation
Getting Started
go get github.com/oracle/coherence-go-client@latest
After executing this command coherence-go-client is ready to use, and it's source will be in:
$GOPATH/pkg/mod/github.com/oracle/coherence-go-client@latest
What's Changed
- Add name service resolver by @tmiddlet2666 in #88
- Refactor queues example by @tmiddlet2666 in #89
- Minor doc by @tmiddlet2666 in #90
Full Changelog: v1.2.0...v1.2.1