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

BlockStreamInfo migration logic needs to run in a Schema of the latest version #15899

Open
tinker-michaelj opened this issue Oct 7, 2024 · 0 comments · May be fixed by #15904
Open

BlockStreamInfo migration logic needs to run in a Schema of the latest version #15899

tinker-michaelj opened this issue Oct 7, 2024 · 0 comments · May be fixed by #15904
Assignees
@tinker-michaelj

Comments

@tinker-michaelj
Copy link
Collaborator

Description

Putting the BlockStreamInfo migration in a 0.54 Schema here assumes we are enabling a non-RECORDS stream mode in 0.55, which is not true.

Instead we need a Schema dedicated to doing this migration which uses an idempotent restart() override to guarantee BlockStreamInfo is always initialized.

Steps to reproduce

As above.

Additional context

No response

Hedera network

other

Version

develop

Operating system

None
@tinker-michaelj tinker-michaelj self-assigned this Oct 7, 2024
@tinker-michaelj tinker-michaelj linked a pull request Oct 8, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tinker-michaelj tinker-michaelj

Labels
None yet
Projects
Services Team
Status: 👀 In Review
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: support restarting from RECORDS -> BOTH hashgraph/hedera-services
1 participant
@tinker-michaelj