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

update Subgraph Studio archive policy #684

Merged
merged 6 commits into from
May 29, 2024
+6 −2
Merged

update Subgraph Studio archive policy #684

Show file tree
Hide file tree
Changes from 4 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
cc3172a
add Timestamp scalar
yash251 May 24, 2024
a6176ad
update Subgraph Studio archive policy
yash251 May 24, 2024
8a8e16c
fix style with prettier
yash251 May 24, 2024
a250b7a
fix requested changes
yash251 May 24, 2024
f4bd2e6
remove special case chains and removed ar change
yash251 May 25, 2024
9f76c02
Merge branch 'main' into yash251/subgraph-upgrade-policy
azf20 May 29, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions website/pages/ar/deploying/deploying-a-subgraph-to-hosted.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -284,8 +284,13 @@ Developers will be notified by email if one of their subgraphs has been marked a

## Subgraph Studio subgraph archive policy

When a new version of a subgraph is deployed, the previous version is archived (deleted from the graph-node DB). This only happens if the previous version is not published to The Graph's decentralized network.
A subgraph version in Studio is archived if and only if it meets the following criteria:
Copy link
Contributor

Choose a reason for hiding this comment

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

This change looks like it's in the ar folder rather than the en?

Copy link
Contributor

Choose a reason for hiding this comment

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

Wow nice catch, I missed that haha.


When a subgraph version isn’t queried for over 45 days, that version is archived.
- The version is not published to the network (or pending publish)
- The version is not indexing a "special case" chain (polygon-zkevm, zksync-era, base, etc.)
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this bullet no longer applies (there are no "special case" chains)

- The version was created 45 or more days ago
- The subgraph hasn't been queried in 30 days

In addition, when a new version is deployed, if the subgraph has not been published, then the N-2 version of the subgraph is archived.

Every subgraph affected with this policy has an option to bring the version in question back.
1 change: 1 addition & 0 deletions website/pages/en/developing/creating-a-subgraph.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -281,6 +281,7 @@ We support the following scalars in our GraphQL API:
| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
| `Timestamp` | Scalar for `timestamp` fields for timeseries and aggregations. |
Copy link
Contributor

Choose a reason for hiding this comment

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

This looks like it's the timestamp change from #683? may want to rebase from Master

Copy link
Member Author

Choose a reason for hiding this comment

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

i have never done this. I was looking on google on how to do this but got super confused, can you help me with this?

Copy link
Contributor

Choose a reason for hiding this comment

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

All good, I rebased for now but can walk you through it at a good moment


#### Enums

Expand Down
Loading