[Access] Index Execution Data #4653
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
FVM Benchstat comparisonThis branch with compared with the base branch onflow:master commit a8f28b9 The command Collapsed results for better readability
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
added 5 commits
August 23, 2023 18:05
peterargue
approved these changes
Sep 27, 2023
| Key: id, | ||
| Value: payload.Value(), | ||
| } | ||
| j++ |
zhangchiqing
approved these changes
Sep 28, 2023
koko1123
approved these changes
Sep 28, 2023
peterargue
reviewed
Sep 28, 2023
peterargue
reviewed
Sep 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes: #4639
This PR implements a state execution indexer module. It's broken down into two parts, the worker and indexer. The worker takes care of consuming new execution data from the execution data requester engine. It builds up a jobqueue to process each newly available execution data provided by the execution data requester.
The indexer module makes sure the data it receives is correctly transformed, the range for indexing is validated and it uses the register storage interface to store the data into the index database.
This PR intentionally skips building this module as part of the access node builder since it's not ready to be built yet, and misses root snapshot data ingestion. It also doesn't include an admin command that was created to query registers. Both of those will be additional PRs.
A simple design schema:
