Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add waitForCompletionOrCreateCheckStatusResponse client API #64

Closed
cgillum opened this issue May 27, 2022 · 0 comments · Fixed by #115
Closed

Add waitForCompletionOrCreateCheckStatusResponse client API #64

cgillum opened this issue May 27, 2022 · 0 comments · Fixed by #115
Assignees
Labels
azure-functions This issue is specific to Azure Functions feature-parity This feature is needed for parity with other language SDKs
Milestone

Comments

@cgillum
Copy link
Member

cgillum commented May 27, 2022

Other languages support a client API that allows you to wait for an orchestration to complete and either a) return the output if it completes within the specified timeout or b) return an HTTP 202 response if the timeout expires. The first release of Java doesn't support this, although it's possible to implement manually.

More information on this feature can be found here.

This is an Azure Functions-specific API that will need to be made to the durabletask-azure-functions package.

Once the API exists, the documentation linked above will need to have its sample updated to reference it.

@cgillum cgillum added feature-parity This feature is needed for parity with other language SDKs azure-functions This issue is specific to Azure Functions labels May 27, 2022
@cgillum cgillum added this to the v1.1.0 milestone Jan 18, 2023
@kaibocai kaibocai self-assigned this Jan 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
azure-functions This issue is specific to Azure Functions feature-parity This feature is needed for parity with other language SDKs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants