-
Notifications
You must be signed in to change notification settings - Fork 31
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
External client ignores task hub name configuration #127
Comments
I should have we activated |
Ok I think that I have found the root cause of it durabletask-mssql/src/DurableTask.SqlServer.AzureFunctions/SqlDurabilityProviderFactory.cs Line 90 in 531422c
SqlOrchestrationService orchestrationService = new SqlOrchestrationService(clientOptions.GetOrchestrationServiceSettings(
this.extensionOptions,
this.connectionInfoResolver));
clientProvider = new SqlDurabilityProvider(
orchestrationService,
clientOptions); |
…sing default TestHubName or DurableTaskOption HubName instead of using the specified TaskHub
@cgillum any date for the release or is it possible to have a preview? |
@bhugot the thing that's blocking the release is that I need to put together a suite of schema upgrade/compatibility tests now that we've reached the stable release versions. This will take some time and we don't have a date for it yet. I can get you a preview package if you're okay without it containing any database upgrade compatibility validation. |
Would be great for the preview. |
OK. You can find the preview nuget packages uploaded here: |
Thanks alot |
Hello,
When using an external client with sql provider. the specified task hub is ignored. The only way to have the specified task hub used is actually to use this
But it's only one taskhub that could be use this way. And we need to be able to ask for many task hub on same sql schema.
What we do is
The text was updated successfully, but these errors were encountered: