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

Add a fast and reliable way to check history #200

Closed
2opremio opened this issue Jun 6, 2024 · 0 comments
Closed

Add a fast and reliable way to check history #200

2opremio opened this issue Jun 6, 2024 · 0 comments

Comments

@2opremio
Copy link
Contributor

2opremio commented Jun 6, 2024

We should have a fast and reliable way to know what has been ingested and if there are any problems (e.g. gaps).

The new transactions DB backend provides GetLedgerRange, using the metadata sequences, but we should at least index that field (I wonder what the performance is in current code :S).

The method should be thorough and have some (at least minimal) consistency checks to detect things like gaps, partially ingested data etc ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

2 participants