Releases: configcat/java-sdk
Releases · configcat/java-sdk
v7.0.2
v7.0.1
v7.0.0
Fixed
- During an ongoing fetch, all additional fetch requests will subscribe to the ongoing fetch's
CompletableFuture
. - JSON deserialization happens only when the actual JSON differs from the cached one in memory.
- The evaluation logs are staying on
info
level but they are now combined into a single log entry.
Added
- A new
logLevel()
configuration option was added, to let the user change the SDK's verbosity. - A
getAllValues()
function was added that evaluates all flags & settings in aMap<String, Object>
. - New
flagOverrides()
builder option to support the reading of flags & settings from a local file or aMap<String, Object>
.
Breaking Changes
- Fixed the names of the Polling modes: e.g:
PollingModes.AutoPoll()
->PollingModes.autoPoll()
. maxWaitTimeForSyncCallsInSeconds
was replaced withmaxInitWaitTimeInSeconds
in case of auto poll to give a maximum amount of wait time for the first config JSON fetch. When it's reached without a result, the latest cached value will be returned.
v6.0.1
v6.0.0
Addressing global data handling and processing trends via Data Governance feature. Customers can control the geographic location where their config JSONs get published to. See the docs.
We are introducing a new DataGovernance initialization parameter. Set this parameter to be in sync with the Data Governance preference on the Dashboard.
Breaking change:
- Custom cache implementations should implement the new cache interface using key parameter in the get/set methods.