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.

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

[FEATURE REQ] BlobChangeFeed client returns valid continuation token at the end of enumeration #48012

Open
MalcolmMcNeely opened this issue Jan 29, 2025 · 1 comment
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files)

Comments

@MalcolmMcNeely
Copy link

MalcolmMcNeely commented Jan 29, 2025

Library name

Azure.Storage.Blobs.ChangeFeed

Please describe the feature.

We want to use the blob change feed to enumerate all items one day and on another day continue the enumeration where we left off, so we don't enumerate the whole thing every time. Previously we relied on the continuation token returns by the enumerator and this looked to be in keeping with the documentation: https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blob-change-feed-how-to#resume-reading-records-from-a-saved-position

However, going from version 12.0.0-preview.29 to 12.0.0-preview.52, the continuation token is now null at the end of enumeration. Rather than saving the last not-null token, or converting the whole project to access the change feed using date based mechanics, it would be great if we got a valid token at the end which we could use later.

Addendum: testing this out it seems that sometimes the enumerator returns a null continuation cursor, but at other times it doesn't. Would be great if this behaviour could be consistent.

@github-actions github-actions bot added Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files) labels Jan 29, 2025
Copy link

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

No branches or pull requests

1 participant