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

Update the migration guide to document that processor checkpoints from legacy versions are not applied #11374

Closed
jsquire opened this issue Apr 16, 2020 · 0 comments
Assignees
Labels
blocking-release Blocks release Client This issue points to a problem in the data-plane of the library. Docs Event Hubs
Milestone

Comments

@jsquire
Copy link
Member

jsquire commented Apr 16, 2020

Summary

In order to align with the goal of supporting cross-language checkpoints and a more efficient means of tracking partition ownership, the EventProcessorClient does not consider or apply checkpoints created with the legacy Microsoft.Azure.EventHubs.Processor family of types. This is a potential area of confusion and should be highlighted for consideration within the migration guide.

Scope of Work

  • Enhance the migration guide to call out that checkpoints and ownership data are not carried forward from the legacy Event Hubs processor types.

  • Consider adding instructions to manually copy/apply the data between formats or a tool to perform the migration of checkpoint data from the legacy format.

Success Criteria

  • The migration guide documents the behavior of the EventProcessorClient regarding legacy checkpoints and sets clear expectations for developers migrating to the new library.

Related Items

  • Create a utility to demonstrate migration of legacy checkpoints for use with the EventProcessorClient (#11373)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
blocking-release Blocks release Client This issue points to a problem in the data-plane of the library. Docs Event Hubs
Projects
None yet
Development

No branches or pull requests

1 participant