Can Multiple Cosmos Trigger Functions on same Cosmos DB Container read different change feeds (documents) for parallel processing?

[ranjeetkpGit]

Hi,

Can Multiple Cosmos Trigger Functions (not instances) on same Cosmos DB Container read different change feeds (documents) for parallel processing?

I mean, if there are multiple changed Cosmos documents, they can be processed from multiple functions and each function have new document only not processed document from other function. I understand there is 'Change feed pull model in Azure Cosmos DB'.

[bartelink]

The more info you can provide about your overall ask, the better people will be able to provide you with guidance; your question is extremely high level.
In general, the principle on which changefeed functionality works is that there is 'a cursor' per physical range.

Each 'processor name' is a cursor (or set of cursors), so one way to get three sets of processing to happen concurrently is to configure three processors (but there will be no coordination across those three sets of work, whic is not what you're after)

Each pull takes a batch of documents from a single physical partition. The work for each normally runs entirely separated. The way the partitions hash mean each assigned processor per range is guaranteed to be working on separate documents.

If you have a 60GB container, you will have at least two partitions. If you have <50 you may not.

[ealsur]

@ranjeetkpGit I am not sure I understand your question.

Are you referring to this: https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/how-to-create-multiple-cosmos-db-triggers which covers how to have multiple independent Azure Functions CosmosDBTriggers configured to listen in the same monitored container?

[ealsur]

I transferred the Issue to the correct repository. Issues about Azure Functions Extensions do not belong on the Cosmos DB SDK repository.