Shahab TajikandDavid Reiss
9547db2e56
## What changed? <!-- Describe what has changed in this PR --> Assigning a task to the appropriate build ID based on the versioning assignment rules. For now, both old and new versioning data is supported, in the following manner - tasks for unassigned (new) workflows/activities -> first try assignment rules, if there is no matching assignment rules fallback to default version set. - tasks of existing versioned executions -> if the build id is part of a version set keep using the version set, otherwise, assume user intends to use the new API and use a dedicated queue for the build ID. - This means we no longer created "guessed" version sets for "unkown" build IDs - tasks of existing unversioned executions -> stays unversioned ## Why? <!-- Tell your future self why have you made these changes --> Part of new Worker Versioning API ## How did you test it? <!-- How have you verified this change? Tested locally? Added a unit test? Checked in staging env? --> Unit tests, functional test will come when the API for adding rules is implemented. ## Potential risks <!-- Assuming the worst case, what can be broken when deploying this change to production? --> Because we no longer created "guessed" version sets for "unkown" build IDs, users of old WV API may "loose" tasks in extremely rare situations. But that is expected for the old API given its private preview stage. ## Is hotfix candidate? <!-- Is this PR a hotfix candidate or does it require a notification to be sent to the broader community? (Yes/No) --> No.
Temporal
Temporal is a durable execution platform that enables developers to build scalable applications without sacrificing productivity or reliability. The Temporal server executes units of application logic called Workflows in a resilient manner that automatically handles intermittent failures, and retries failed operations.
Temporal is a mature technology that originated as a fork of Uber's Cadence. It is developed by Temporal Technologies, a startup by the creators of Cadence.
Learn more:
Getting Started
Download and Start Temporal Server Locally
Execute the following commands to start a pre-built image along with all the dependencies.
brew install temporal
temporal server start-dev
Refer to Temporal CLI documentation for more installation options.
Run the Samples
Clone or download samples for Go or Java and run them with the local Temporal server. We have a number of HelloWorld type scenarios available, as well as more advanced ones. Note that the sets of samples are currently different between Go and Java.
Use CLI
Use Temporal CLI to interact with the running Temporal server.
temporal operator namespace list
temporal workflow list
Use Temporal Web UI
Try Temporal Web UI by opening http://localhost:8233 for viewing your sample workflows executing on Temporal.
Repository
This repository contains the source code of the Temporal server. To implement Workflows, Activities and Workers, use one of the supported languages.
Contributing
We'd love your help in making Temporal great. Please review the internal architecture docs and our contribution guide.
If you'd like to work on or propose a new feature, first peruse feature requests and our proposals repo to discover existing active and accepted proposals.
Feel free to join the Temporal community forum or Slack to start a discussion or check if a feature has already been discussed. Once you're sure the proposal is not covered elsewhere, please follow our proposal instructions or submit a feature request.