Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EventProcessorClient and maintaining checkpoints in the Storage Account #2441

Open
kobelev-dev opened this issue Jul 19, 2024 · 0 comments
Open
Labels

Comments

@kobelev-dev
Copy link

kobelev-dev commented Jul 19, 2024

Dear sirs,

Azure SDK contains abstract class Azure.Messaging.EventHubs.Primitives.CheckpointStore. This implies that users may want to create their own implementations. Great.

At the same time, from what I see, all constructors of the EventProcessorClient class use Azure.Storage.Blobs.BlobContainerClient as a parameter. This limits use of EventProcessorClient class only to the BlobCheckpointStore and not any other. I see that packages for other languages offer more, like Redis. So, my questions:

  1. Am I missing something? Can it be that there is some trick that allows using EventProcessorClient with the custom check point sore? Note that I know about issue with multiple instances of EventProcessorClient and their need to have access to the same checkpoint store. My application for numerous reasons needs its own store. Is that possible?
  2. Is there any other class that allows that? It may happen that I am looking at a wrong class. I am interested in .Net/C# solution.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant