Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

graphprotocol / graph-node Public

Notifications You must be signed in to change notification settings
Fork 1k
Star 3k

Code
Issues 485
Pull requests 51
Actions
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Security
Insights

Copy subgraph data in batches when grafting#2293

Merged

lutter merged 11 commits intomastergraphprotocol/graph-node:masterfrom lutter/graftgraphprotocol/graph-node:lutter/graftCopy head branch name to clipboard

Apr 21, 2021

+956-133

Conversation Commits11 (11)Checks Files changed

Commits

Commits on Apr 20, 2021

graph, store: Copy subgraph data in batches
lutter
committed
store: Use the copy module to copy subgraph data for grafting
lutter
committed
store: Do not remove deployments that are the source of an active copy
lutter
committed
store: Log progress while copying subgraph data
lutter
committed
store: Use Site.id in deployment::exists
lutter
committed
store: Make data copying possible across shards
lutter
committed
store: Map the metadata from foreign databases into each shard
lutter
committed
store: Copy metadata across shards and allow cross-shard grafting
lutter
committed
store: Use 'exists' instead of 'count(*) > 0' in a few places
lutter
committed
store: Make sure we only copy the data that we set out to copy
lutter
committed
store: Copy only necessary DDS so we don't need to revert them
lutter
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.