docs: datastore migration guide#8581
Closed
cadivus wants to merge 4 commits into
Closed
Conversation
…flict resolution cleanup (#8578)
* docs: Add Flutter guide * docs: Don't mention Apollo in the backend part * docs: Add Android guide * docs: Add Swift guide * docs: Update spellcheck
osama-rizk
reviewed
Apr 29, 2026
|
|
||
| <InlineFilter filters={["angular", "javascript", "nextjs", "react", "react-native", "vue"]}> | ||
|
|
||
| This guide shows you how to use Apollo Client for queries, mutations, and caching, combined with the Amplify library's built-in subscription support for real-time updates. Depending on how much of DataStore's feature set your app actually uses, you may find the migration simpler than expected. |
Contributor
There was a problem hiding this comment.
Can we add link here to the "Apollo Client" docs?
osama-rizk
previously approved these changes
Apr 29, 2026
15 tasks
soberm
approved these changes
Apr 30, 2026
osama-rizk
approved these changes
Apr 30, 2026
Contributor
|
This is now included in #8570 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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
Updates the DataStore-to-GraphQL migration guide to include backend changes required for a zero-downtime migration.
Problem
PR #8540 assumes clients can keep their Gen1 backend with DataStore/conflict resolution enabled. This is incorrect because:
_deleted: true) remain in DynamoDB_deletedin the schema, clients cannot filter them outSolution
This PR documents the correct migration approach:
amplify update api_deleted: Booleanto the GraphQL schema (maps to existing DynamoDB data)amplify pushto apply changes{ _deleted: { ne: true } }_deletedfield once all clients are migratedWhy this approach?
Files changed
src/directory/directory.mjs— Added navigation entries for the new migration guide pagessrc/pages/gen1/[platform]/.../migrate-from-datastore/index.mdx— Parent page explaining why backend changes are requiredsrc/pages/gen1/[platform]/.../migrate-from-datastore/disable-conflict-resolution/index.mdx— Step-by-step guide for disabling conflict resolutionTesting
yarn prebuildgenerates directory.json successfully with new entriesRelated: #8540