Add support for Azure Table Persistence v3 in the exporter tool #98
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
boblangley
changed the title
danielmarbach
changed the title
danielmarbach
force-pushed
the
support-asp
branch
from
4ecef76 to
6cba15f
Compare
SeanFeldman
approved these changes
Nov 17, 2020
...sistence.CosmosDB.AzureStorageSagaExporter.Asp3.AcceptanceTests/NServiceBusAcceptanceTest.cs
Show resolved
Hide resolved
danielmarbach
changed the title
danielmarbach
added
Feature
bug
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Azure Table Persistence 3 supports determinstic IDs that use the same approach as Cosmos DB persister. If customers want to migrate from Azure Table Persistence v3 towards Cosmos SQL API we can handle the cases where the saga id is already in the correct format.