Cadence is a distributed, scalable, durable, and highly available orchestration engine to execute asynchronous long-running business logic in a scalable and resilient way.
make pr
target for an easy "do automated checks for PR" command by @Groxx in https://github.com/uber/cadence/pull/5670
Full Changelog: https://github.com/uber/cadence/compare/v1.2.7...v1.2.8
workflow query-types
command to CLI by @arzonus in https://github.com/uber/cadence/pull/5456
Full Changelog: https://github.com/uber/cadence/compare/v1.2.6...v1.2.7
Full Changelog: https://github.com/uber/cadence/compare/v1.2.5...v1.2.6
Full Changelog: https://github.com/uber/cadence/compare/v1.2.4...v1.2.5-prerelease3
Full Changelog: https://github.com/uber/cadence/compare/v1.2.3...v1.2.4
Full Changelog: https://github.com/uber/cadence/compare/v1.2.1...v1.2.2
Expose workflow history size and count to client by @timl3136 (#5392)
[cadence-cli] fix typo in input flag for parallelism by @sankari165 (#5397)
Update config store client to support SQL database by @Shaddoll (#5395) Scaffold config store for sql plugins by @Shaddoll (#5396) Improve poller detection for isolation by @Shaddoll (#5399)
Not much. Primarily that we are declaring "it's stable and in use" more visibly, because we continually get questions about this :) A larger public announcement / state-of-the-project is in the works.
Importantly, v1.0 does not imply any change to backwards compatibility (the minimum supported client version has not changed), RPC compatibility (ditto, all changes are backwards compatible), or Go API compatibility (this is not truly a library, Go compatibility is not a goal).
Going by previous version patterns, this would have been labeled v0.26.0 as it is a relatively incremental change (plus schema changes) from v0.25.0. As such, some strings still reference "0.26", because this older SHA is the one we have been using the most internally.
These strings will be updated and validated soon, and will likely be released as v1.0.1. This should have no behavioral impact at all, but will be visible in metrics, logs, and display strings.
There have been schema changes to both normal and visibility datastores, primarily to provide better data for cleanup and hot-shard detection:
These were intentionally kept out of v0.25.0 to keep that upgrade simple, as they were not fully utilized yet.
We have internally disabled the replication cache (history.replicatorCacheCapacity
dynamic config set to 0
), due to unexpectedly large memory use under abnormal load, and you may wish to do so as well.
We did not encounter any misbehavior, and it did reduce database load as intended, but we intend to make some changes to it to estimate and constrain memory use before re-enabling.
At a very high level, we've been focused on:
Some loosely categorized PRs that were included follows:
T.TempDir
to create temporary test directory by @Juneezee in https://github.com/uber/cadence/pull/5013
maxQPS
from sql plugin documentation by @mantas-sidlauskas in https://github.com/uber/cadence/pull/5107
Full Changelog: https://github.com/uber/cadence/compare/v0.25.0...v1.0.0
history.replicatorCacheCapacity:
- value: 0