CosmosDBTrigger on Azure Function without Lease Collection
I have an Azure Function which is triggered each time that one on more items in my CosmosDb Collection is updated.
The code works correctly:
[StorageAccount("AzureWebJobsStorage")]
public static class ChangeFeedFunction
{
[FunctionName("ChangeFeedFunction")]
public static void ChangeFeedFunction(
[CosmosDBTrigger(
databaseName: "MyDataBase",
collectionName: "MyCollection",
ConnectionStringSetting = "CosmosDbConnectionString",
LeaseCollectionName = "MyCollection_Leases",
CreateLeaseCollectionIfNotExists = true
)] IReadOnlyList<Document> documents,
[Queue("collection-changes")] ICollector<Message> analystQueue,
ILogger logger
)
{
//Operations;
}
But in the case, it means I have 2 CosmosDb Collections (MyCollection and MyCollection_Leases) which is minimum 40$ per month. I would like to reduce the cost. Is there a way to observe the modification on my CosmosDb Collection without using another CosmosDb Collection?
Thanks
azure-functions azure-cosmosdb
add a comment |
I have an Azure Function which is triggered each time that one on more items in my CosmosDb Collection is updated.
The code works correctly:
[StorageAccount("AzureWebJobsStorage")]
public static class ChangeFeedFunction
{
[FunctionName("ChangeFeedFunction")]
public static void ChangeFeedFunction(
[CosmosDBTrigger(
databaseName: "MyDataBase",
collectionName: "MyCollection",
ConnectionStringSetting = "CosmosDbConnectionString",
LeaseCollectionName = "MyCollection_Leases",
CreateLeaseCollectionIfNotExists = true
)] IReadOnlyList<Document> documents,
[Queue("collection-changes")] ICollector<Message> analystQueue,
ILogger logger
)
{
//Operations;
}
But in the case, it means I have 2 CosmosDb Collections (MyCollection and MyCollection_Leases) which is minimum 40$ per month. I would like to reduce the cost. Is there a way to observe the modification on my CosmosDb Collection without using another CosmosDb Collection?
Thanks
azure-functions azure-cosmosdb
add a comment |
I have an Azure Function which is triggered each time that one on more items in my CosmosDb Collection is updated.
The code works correctly:
[StorageAccount("AzureWebJobsStorage")]
public static class ChangeFeedFunction
{
[FunctionName("ChangeFeedFunction")]
public static void ChangeFeedFunction(
[CosmosDBTrigger(
databaseName: "MyDataBase",
collectionName: "MyCollection",
ConnectionStringSetting = "CosmosDbConnectionString",
LeaseCollectionName = "MyCollection_Leases",
CreateLeaseCollectionIfNotExists = true
)] IReadOnlyList<Document> documents,
[Queue("collection-changes")] ICollector<Message> analystQueue,
ILogger logger
)
{
//Operations;
}
But in the case, it means I have 2 CosmosDb Collections (MyCollection and MyCollection_Leases) which is minimum 40$ per month. I would like to reduce the cost. Is there a way to observe the modification on my CosmosDb Collection without using another CosmosDb Collection?
Thanks
azure-functions azure-cosmosdb
I have an Azure Function which is triggered each time that one on more items in my CosmosDb Collection is updated.
The code works correctly:
[StorageAccount("AzureWebJobsStorage")]
public static class ChangeFeedFunction
{
[FunctionName("ChangeFeedFunction")]
public static void ChangeFeedFunction(
[CosmosDBTrigger(
databaseName: "MyDataBase",
collectionName: "MyCollection",
ConnectionStringSetting = "CosmosDbConnectionString",
LeaseCollectionName = "MyCollection_Leases",
CreateLeaseCollectionIfNotExists = true
)] IReadOnlyList<Document> documents,
[Queue("collection-changes")] ICollector<Message> analystQueue,
ILogger logger
)
{
//Operations;
}
But in the case, it means I have 2 CosmosDb Collections (MyCollection and MyCollection_Leases) which is minimum 40$ per month. I would like to reduce the cost. Is there a way to observe the modification on my CosmosDb Collection without using another CosmosDb Collection?
Thanks
azure-functions azure-cosmosdb
azure-functions azure-cosmosdb
asked Nov 14 '18 at 19:14
Cedric Arnould
336213
336213
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Following the cosmos db trigger function document, the lease
collection can't be avoid so far because it bears important responsibility.
We need one lease
collection when using the Trigger to store the checkpoints for each Function. Let me say that if there are 10 documents were inserted into cosmos db, the trigger function was triggered one by one and the checkpoint moved with the process and stored into lease
collection. Suddently, the trigger shut down resulted from some reasons. During this time, 5 more documents inserted into db. After the trigger function restarting, it knows from which node to continue the execution function with the checkpoint in lease
collection.(I wish I had made it clear...)
BTW,you could share one single lease
collection for all of your collection for a more cost-effective approach. Please refer to this article.
As for the cost,you could create the minimum configured lease
collection. And the cost on the portal is estimated value. The price based on the consumption of RUs. Please refer to this document.
Thanks for your answer!
– Cedric Arnould
Nov 15 '18 at 19:27
@CedricArnould You're welcome!
– Jay Gong
Nov 16 '18 at 1:27
add a comment |
I would suggest scaling the database rather than the collection. If you scaled the database at 400 RU/s you can share that across collections.
Thanks for your comment
– Cedric Arnould
2 days ago
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53307280%2fcosmosdbtrigger-on-azure-function-without-lease-collection%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Following the cosmos db trigger function document, the lease
collection can't be avoid so far because it bears important responsibility.
We need one lease
collection when using the Trigger to store the checkpoints for each Function. Let me say that if there are 10 documents were inserted into cosmos db, the trigger function was triggered one by one and the checkpoint moved with the process and stored into lease
collection. Suddently, the trigger shut down resulted from some reasons. During this time, 5 more documents inserted into db. After the trigger function restarting, it knows from which node to continue the execution function with the checkpoint in lease
collection.(I wish I had made it clear...)
BTW,you could share one single lease
collection for all of your collection for a more cost-effective approach. Please refer to this article.
As for the cost,you could create the minimum configured lease
collection. And the cost on the portal is estimated value. The price based on the consumption of RUs. Please refer to this document.
Thanks for your answer!
– Cedric Arnould
Nov 15 '18 at 19:27
@CedricArnould You're welcome!
– Jay Gong
Nov 16 '18 at 1:27
add a comment |
Following the cosmos db trigger function document, the lease
collection can't be avoid so far because it bears important responsibility.
We need one lease
collection when using the Trigger to store the checkpoints for each Function. Let me say that if there are 10 documents were inserted into cosmos db, the trigger function was triggered one by one and the checkpoint moved with the process and stored into lease
collection. Suddently, the trigger shut down resulted from some reasons. During this time, 5 more documents inserted into db. After the trigger function restarting, it knows from which node to continue the execution function with the checkpoint in lease
collection.(I wish I had made it clear...)
BTW,you could share one single lease
collection for all of your collection for a more cost-effective approach. Please refer to this article.
As for the cost,you could create the minimum configured lease
collection. And the cost on the portal is estimated value. The price based on the consumption of RUs. Please refer to this document.
Thanks for your answer!
– Cedric Arnould
Nov 15 '18 at 19:27
@CedricArnould You're welcome!
– Jay Gong
Nov 16 '18 at 1:27
add a comment |
Following the cosmos db trigger function document, the lease
collection can't be avoid so far because it bears important responsibility.
We need one lease
collection when using the Trigger to store the checkpoints for each Function. Let me say that if there are 10 documents were inserted into cosmos db, the trigger function was triggered one by one and the checkpoint moved with the process and stored into lease
collection. Suddently, the trigger shut down resulted from some reasons. During this time, 5 more documents inserted into db. After the trigger function restarting, it knows from which node to continue the execution function with the checkpoint in lease
collection.(I wish I had made it clear...)
BTW,you could share one single lease
collection for all of your collection for a more cost-effective approach. Please refer to this article.
As for the cost,you could create the minimum configured lease
collection. And the cost on the portal is estimated value. The price based on the consumption of RUs. Please refer to this document.
Following the cosmos db trigger function document, the lease
collection can't be avoid so far because it bears important responsibility.
We need one lease
collection when using the Trigger to store the checkpoints for each Function. Let me say that if there are 10 documents were inserted into cosmos db, the trigger function was triggered one by one and the checkpoint moved with the process and stored into lease
collection. Suddently, the trigger shut down resulted from some reasons. During this time, 5 more documents inserted into db. After the trigger function restarting, it knows from which node to continue the execution function with the checkpoint in lease
collection.(I wish I had made it clear...)
BTW,you could share one single lease
collection for all of your collection for a more cost-effective approach. Please refer to this article.
As for the cost,you could create the minimum configured lease
collection. And the cost on the portal is estimated value. The price based on the consumption of RUs. Please refer to this document.
answered Nov 15 '18 at 2:01
Jay Gong
8,0061512
8,0061512
Thanks for your answer!
– Cedric Arnould
Nov 15 '18 at 19:27
@CedricArnould You're welcome!
– Jay Gong
Nov 16 '18 at 1:27
add a comment |
Thanks for your answer!
– Cedric Arnould
Nov 15 '18 at 19:27
@CedricArnould You're welcome!
– Jay Gong
Nov 16 '18 at 1:27
Thanks for your answer!
– Cedric Arnould
Nov 15 '18 at 19:27
Thanks for your answer!
– Cedric Arnould
Nov 15 '18 at 19:27
@CedricArnould You're welcome!
– Jay Gong
Nov 16 '18 at 1:27
@CedricArnould You're welcome!
– Jay Gong
Nov 16 '18 at 1:27
add a comment |
I would suggest scaling the database rather than the collection. If you scaled the database at 400 RU/s you can share that across collections.
Thanks for your comment
– Cedric Arnould
2 days ago
add a comment |
I would suggest scaling the database rather than the collection. If you scaled the database at 400 RU/s you can share that across collections.
Thanks for your comment
– Cedric Arnould
2 days ago
add a comment |
I would suggest scaling the database rather than the collection. If you scaled the database at 400 RU/s you can share that across collections.
I would suggest scaling the database rather than the collection. If you scaled the database at 400 RU/s you can share that across collections.
answered Jan 3 at 21:26
Dillorscroft
143129
143129
Thanks for your comment
– Cedric Arnould
2 days ago
add a comment |
Thanks for your comment
– Cedric Arnould
2 days ago
Thanks for your comment
– Cedric Arnould
2 days ago
Thanks for your comment
– Cedric Arnould
2 days ago
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53307280%2fcosmosdbtrigger-on-azure-function-without-lease-collection%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown