Could GetChangeFeedIterator FeedResponse include Headers.Session? #4263
Replies: 1 comment
-
I've noticed this discussion forum doesn't get a lot of attention, so I've opened an issue: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a pull-based change feed consumer that reacts to certain changes by putting a message on a service bus queue to be handled by another process downstream. I don't include the actual document in the service bus queue because the downstream process may not need it, and will likely need other documents in the same partition, so that process is designed to work independently, knowing just the partition ID it's working with.
The problem is that we're using session consistency and sometimes the change consumer becomes aware of a new document, but the downstream process doesn't get that document when it reads all the documents out of the partition.
Correct me if I'm wrong, but I believe I could use the token from the first read to ensure that the downstream read at least includes the changed document, but
FeedResponse<T>.Headers.Session
always come back null using the pull model. I've confirmed that it is populated when using the change feed processor, so I'm hoping the SDK can be updated to include it when using the pull model. Though maybe the session token from the change feed read won't work to coordinate a normal document read?Beta Was this translation helpful? Give feedback.
All reactions