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.

Sign up for GitHub

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

Jump to bottom

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

Closed
jsquire opened this issue Apr 17, 2020 · 1 comment
Closed

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

jsquire opened this issue Apr 17, 2020 · 1 comment
Assignees
@chradek
Labels
Client This issue points to a problem in the data-plane of the library. Docs Event Hubs
Milestone
[2020] June

Comments

@jsquire
Copy link
Member

jsquire commented Apr 17, 2020 •
edited
Loading

Summary

In order to align with the goal of supporting cross-language checkpoints and a more efficient means of tracking partition ownership, the current Event Hub Consumer Client does not consider or apply checkpoints created with the legacy Event Processor Host 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 Event Hub Consumer Client regarding legacy checkpoints and sets clear expectations for developers migrating to the new library.
@jsquire jsquire added Client This issue points to a problem in the data-plane of the library. Event Hubs Docs needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Apr 17, 2020
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Apr 17, 2020
@jsquire jsquire added the needs-team-triage Workflow: This issue needs the team to triage. label Apr 17, 2020
@ramya-rao-a ramya-rao-a added this to the [2020] May milestone Apr 17, 2020
@ramya-rao-a ramya-rao-a removed the needs-team-triage Workflow: This issue needs the team to triage. label Apr 17, 2020
@ramya-rao-a ramya-rao-a assigned ramya-rao-a and unassigned chradek Apr 27, 2020
@ramya-rao-a ramya-rao-a assigned chradek and unassigned ramya-rao-a May 6, 2020
@ramya-rao-a ramya-rao-a modified the milestones: [2020] May, [2020] June May 6, 2020
@chradek chradek mentioned this issue Jun 5, 2020
Merged
@chradek
Copy link
Contributor

chradek commented Jun 8, 2020

This has been addressed by #9342.

@chradek chradek closed this as completed Jun 8, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@chradek chradek

Labels
Client This issue points to a problem in the data-plane of the library. Docs Event Hubs
Projects
None yet
Milestone
[2020] June
Development

No branches or pull requests
3 participants
@jsquire @ramya-rao-a @chradek