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

coordinator: implement history with fs store backend #522

Merged
merged 1 commit into from
Jun 6, 2024
Merged

Conversation

katexochen
Copy link
Member

This is the history storage module and part of the implementation of RFC 004.

@katexochen katexochen added the no changelog PRs not listed in the release notes label Jun 4, 2024
@katexochen katexochen requested a review from burgerdev June 4, 2024 13:27
coordinator/history/fsstore.go Outdated Show resolved Hide resolved
coordinator/history/history.go Outdated Show resolved Hide resolved
coordinator/history/history.go Outdated Show resolved Hide resolved
coordinator/history/history.go Outdated Show resolved Hide resolved
coordinator/history/history.go Outdated Show resolved Hide resolved
coordinator/history/history.go Outdated Show resolved Hide resolved
coordinator/history/history.go Outdated Show resolved Hide resolved
coordinator/history/fsstore.go Outdated Show resolved Hide resolved
coordinator/history/history.go Outdated Show resolved Hide resolved
coordinator/history/history.go Outdated Show resolved Hide resolved
coordinator/history/history.go Show resolved Hide resolved
coordinator/history/history_test.go Outdated Show resolved Hide resolved
coordinator/history/history.go Show resolved Hide resolved
}

// GetLatest returns the verified transition for the given hash.
func (h *History) GetLatest() (*LatestTransition, error) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While implementing I realized that I need to be able to tell the difference between generic errors and "no latest set".

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The issue is that I'd like to update my local state from persistency before handling a SetManifest, when I don't yet have something to CompareAndSet. But I can work around that by ignoring errors when my local state suggests emptiness - I will be stopped at the very latest when my update conflicts. So this would be a good extension, but not necessary right now.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

use errors.Is(err, os.ErrNotExist) ?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can do that for now, but it's somewhat counter to the idea of having pluggable KV stores :)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

True.

Copy link
Member

@3u13r 3u13r left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@katexochen katexochen merged commit ae59992 into main Jun 6, 2024
8 checks passed
@katexochen katexochen deleted the p/store branch June 6, 2024 06:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no changelog PRs not listed in the release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants