Container.GetChangeFeedProcessorBuilder().WithStartTime() not working anymore with 3.15
See original GitHub issueWe are continuously addressing and improving the SDK, if possible, make sure the problem persist in the latest SDK version. The Problem only occurrs with the latest version
Describe the bug The changefeed processor always starts at the beginning, even when given a specific time
To Reproduce
- Use Library in Version 3.15.0 example code:
var changeFeedProcessor = sourceContainer
.GetChangeFeedProcessorBuilder(processorName, this.changesHandler)
.WithStartTime(this.startTime)
Expected behavior The first dataset shouldn’t be months before the given “startTime”
Actual behavior The first dataset IS months before the given “startTime”.
BUT: Downgrading the library (without changing any single line of code) solves the problem.
Of course, after every attempt, you have to delete your lease-collection, to ensure the startTime is considered at all!
Environment summary SDK Version: 3.15.0 OS Version: Win 10
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Cosmos Db Change Feed do not give the desired result
I am trying to get all the changes from my monitored Db in the Cosmos db Change Feed by following the below codes....
Read more >Cosmos Db Change Feed do not give the desired result
So I created a new container, gave the Id for it as Lease Container in my above code and set Time to be...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
ok, finally the promised update: Had the chance to update the library in our product and tested the replay from a specific date - works fine now! 😃
Thanks for fixing this so quickly!
@j82w :Thank you for the update! I added a story to our product backlog, but it’ll take at least another 2-4 weeks until it’s processed. Since you were able to reproduce the issue, I’m pretty sure it’ll work for us, if it works for you now 😃