Change feed processor cannot read from the beginning

Describe the bug A ChangeFeedProcessor configured to read from the beginner per this page is never fed any records.

To Reproduce Clone https://github.com/CMihalcik/cosmosdb-change-feed-from-beginning, add Cosmos credentials and run.

Expected behavior The processor’s ChangesHandler delegate is called with the earliest items in the collection.

Actual behavior The processor’s ChangesHandler delegate is never called.

Environment summary SDK Version: 3.3.2 OS Version: macOS 10.13.6

Additional context When the change feed processor is configured this way, it doesn’t seem to be called with any items, even those created after the processor is started.

[bartelink]

I haven’t looked at your example, was only trying to rule out stupid stuff 😉 (I’m still using V2 as some critical features I rely on are missing in the V3 rendition so far); perhaps the team will respond in due course.

[timsander1]

Let me just clarify my previous comment to make sure we are talking about the same thing (I think we are but just want to make sure 😃 )

For the 20 different change feed processors (with different processorName and lease container configuration), there’s no dependency on the number of physical partitions. You can create as many of these as you’d like.

For a particular deployment unit, the number of instances is bound by the number of physical partitions. If this upper bound is an issue you could either split up the work between different deployment units (basically make the logic in each delegate quicker to execute) or temporarily raise (then lower) throughput to increase the number of physical partitions. For example, you could try raising throughput to 30,000 RUs then lowering back down to your desired amount a few hours later.

You can track progress on User Voice: https://feedback.azure.com/forums/263030-azure-cosmos-db?filter=top&page=2. I don’t believe this entry has been submitted yet but please feel free to submit and we will post periodic updates.