graph pruning #336
Draft
graph pruning #336
Conversation
This file contains hidden or 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
|
see latest commit CI e2e - graph-node has error to be fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description of the change
Specify pruning of 500 blocks in subgraph schema to ensure low burden on indexers.
fixes https://linear.app/art-blocks/issue/PRO-1294/update-subgraph-spec-pruning-to-500
500 blocks is the upcoming limit supported by the upgrade indexer, and is all that should be needed by our typical indexing operations at Art Blocks.
Complications
The pruning specification was not supported until manifest specVersion: 1.0.0, our subgraph has been defined on specVersion 0.2.0 since it was created. Quite a few updates are required to support this new specVersion, including updating dependencies, node versions, and the graph node e2e image.