-
Notifications
You must be signed in to change notification settings - Fork 493
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
ChangeFeedIterator gets stuck on multihashed containers for prefix partitions keys that span multiple physical partitions. #3865
Labels
bug
Something isn't working
HierarchicalPartitioning
Tag to track issues related to Hierarchical Partitioned containers
Hotfix
A hotfix is required for the issue
Comments
NaluTripician
added
bug
Something isn't working
Hotfix
A hotfix is required for the issue
labels
May 19, 2023
NaluTripician
changed the title
ChangeFeedIterator gets stuck on multihased containers for prefix partitions keys that span multiple physical partitions.
ChangeFeedIterator gets stuck on multihashed containers for prefix partitions keys that span multiple physical partitions.
May 19, 2023
Hi, any updates on this? Thanks! |
Working on a hotfix now, should be out next week. |
Any status updates? |
Issue is fixed with latest release of the SDK (3.35.0) |
SrinikhilReddy
added
the
HierarchicalPartitioning
Tag to track issues related to Hierarchical Partitioned containers
label
Sep 21, 2023
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
HierarchicalPartitioning
Tag to track issues related to Hierarchical Partitioned containers
Hotfix
A hotfix is required for the issue
Describe the bug
When reading the
ChangeFeed
for a prefix partition key that spans multiple physical partitions theChangeFeed
will not be able to handle the partition split and will get stuck in an infinite loop.Expected behavior
Results should be returned.
Actual behavior
ReadNextAsync
becomes stuck in an infinite loop.The text was updated successfully, but these errors were encountered: