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.

Sign up for GitHub

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

Jump to bottom

CosmosDB: Is resolving partition and container information deterministic? #6659

Open
ramonsmits opened this issue May 27, 2024 · 0 comments
Open

CosmosDB: Is resolving partition and container information deterministic? #6659

ramonsmits opened this issue May 27, 2024 · 0 comments

Comments

@ramonsmits
Copy link
Member

Is the order of invoking any of the following API's deterministic?

  • ExtractPartitionKeyFromMessages
  • ExtractPartitionKeyFromHeader
  • ExtractContainerInformationFromHeader
  • ExtractContainerInformationFromMessage
  • IPartitionKeyFromMessageExtractor
  • IPartitionKeyFromHeadersExtractor
  • IContainerInformationFromHeadersExtractor
  • IContainerInformationFromMessagesExtractor

Meaning, in what order is the partition key / container information resolved?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ramonsmits