azure-documentdb-changefeedprocessor-dotnet | library provides a host for distributing change feed events | Azure library

by Azure C# Version: v2.3.1 License: Non-SPDX

X-Ray Key Features Code Snippets(2)Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | azure-documentdb-changefeedprocessor-dotnet Summary

azure-documentdb-changefeedprocessor-dotnet is a C# library typically used in Cloud, Azure applications. azure-documentdb-changefeedprocessor-dotnet has no bugs, it has no vulnerabilities and it has low support. However azure-documentdb-changefeedprocessor-dotnet has a Non-SPDX License. You can download it from GitHub.

This library provides a host for distributing change feed events in partitioned collection across multiple observers. Instances of the host can scale up (by adding) or down (by removing) dynamically, and the load will be automatically distributed among active instances in about-equal way.

Support

Quality

Security

License

Reuse

Support

azure-documentdb-changefeedprocessor-dotnet has a low active ecosystem.

It has 51 star(s) with 20 fork(s). There are 50 watchers for this library.

It had no major release in the last 12 months.

There are 19 open issues and 46 have been closed. On average issues are closed in 76 days. There are 4 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of azure-documentdb-changefeedprocessor-dotnet is v2.3.1

Quality

azure-documentdb-changefeedprocessor-dotnet has 0 bugs and 0 code smells.

Security

azure-documentdb-changefeedprocessor-dotnet has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

azure-documentdb-changefeedprocessor-dotnet code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

azure-documentdb-changefeedprocessor-dotnet has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

azure-documentdb-changefeedprocessor-dotnet releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of azure-documentdb-changefeedprocessor-dotnet

Get all kandi verified functions for this library.

azure-documentdb-changefeedprocessor-dotnet Key Features

No Key Features are available at this moment for azure-documentdb-changefeedprocessor-dotnet.

azure-documentdb-changefeedprocessor-dotnet Examples and Code Snippets

Example

Lines of Code : 80

License : Non-SPDX (NOASSERTION)

Copy

// Observer.cs
namespace Sample
{
    using System;
    using System.Collections.Generic;
    using System.Threading;
    using System.Threading.Tasks;
    using Microsoft.Azure.Documents;
    using Microsoft.Azure.Documents.ChangeFeedProcessor.FeedP

Change Feed Processor library (v2),Troubleshooting,How to enable tracing

Lines of Code : 24

License : Non-SPDX (NOASSERTION)

Copy

using Microsoft.Azure.Documents.ChangeFeedProcessor.Logging;

var hostName = "SampleHost";
var tracelogProvider = new TraceLogProvider();
using (tracelogProvider.OpenNestedContext(hostName))
{
    LogProvider.SetCurrentLogProvider(tracelogProvider);

Community Discussions

Trending Discussions on azure-documentdb-changefeedprocessor-dotnet

Change Feed Processor Lib does not honour ChangeFeedProcessorOptions FeedPollDelay / CheckPointFrequency

QUESTION

Change Feed Processor Lib does not honour ChangeFeedProcessorOptions FeedPollDelay / CheckPointFrequency

Asked 2019-May-03 at 00:00

I am following this sample code (https://github.com/Azure/azure-documentdb-changefeedprocessor-dotnet#example) to register an observer to process change feed in cosmos db collection. I am creating new documents in the cosmos db collection using a utility (say create 400 documents within a for loop). I am using using FeedPollDelay of 30 seconds. But it doesn't seem to be honoured by CFP lib. ProcessChangesAsync method gets invoked repeatedly even before feed poll delay interval expires. In the first batch, around 60 docs are retrieved and in the second batch around 20 docs are retrieved, in the third batch around 100 docs are retrieved.

...

ANSWER

Answered 2019-May-03 at 00:00

FeedPollDelay is used when the Change Feed Processor reads the Change Feed and finds no new changes, not in-between each batch.

Example flow:

CFP polls for changes, finds X.
ProcessChangesAsync is called with X
After ProcessChangesAsync finishes, CFP immediately polls for changes, finds Y.
ProcessChangesAsync is called with Y.
After ProcessChangesAsync finishes, CFP immediately polls for changes, finds nothing, waits FeedPollDelay.
CFP polls for changes, finds Z.
ProcessChangesAsync is called with Z
After ProcessChangesAsync finishes, CFP immediately polls for changes, finds nothing, waits FeedPollDelay.
Etc….

Source https://stackoverflow.com/questions/55956916

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install azure-documentdb-changefeedprocessor-dotnet

You can download it from GitHub.

Support

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com. When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA. This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Find more information at: