Closed bhugot closed 1 year ago
I should have we activated EXECUTE dt.SetGlobalSetting @Name='TaskHubMode', @Value=0
Ok I think that I have found the root cause of it https://github.com/microsoft/durabletask-mssql/blob/531422c6260bed46495dd91bb4741f1f675a6dc9/src/DurableTask.SqlServer.AzureFunctions/SqlDurabilityProviderFactory.cs#L90 it's creating another SqlOrchestrationService instead of using the one created correctly one line before so it should instead do that
SqlOrchestrationService orchestrationService = new SqlOrchestrationService(clientOptions.GetOrchestrationServiceSettings(
this.extensionOptions,
this.connectionInfoResolver));
clientProvider = new SqlDurabilityProvider(
orchestrationService,
clientOptions);
@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