Skip to content

Commit 9782ba2

Browse files
jwhartleyjshearer
authored andcommitted
Adding instructions for migrating data after storage mapping changes
Added "Migrating your existing data to the new storage mapping" section.
1 parent d9d0458 commit 9782ba2

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

site/docs/getting-started/installation.mdx

+9
Original file line numberDiff line numberDiff line change
@@ -145,3 +145,12 @@ information you gathered per the steps above.
145145
Let us know whether you want to use this storage bucket to for your whole Flow account, or just a
146146
specific [prefix](../concepts/catalogs.md#namespace).
147147
We'll be in touch when it's done!
148+
149+
## Migrating your existing data to the new storage mapping
150+
151+
Once you've created your new storage mapping, your collections will be updated to pick up the new storage mapping,
152+
so new data will be written there. Existing data from your previous storage mapping is not automatically migrated,
153+
to do so you should backfill all of your captures after configuring a storage mapping. Most tenants will have been
154+
using the estuary-public storage mapping on the Free plan to begin with, which expires data after 20 days. By
155+
backfilling all of your captures you guarantee that even though the data from estuary-public will expire, you’ll
156+
still have a full view of your data available on your new storage mapping.

0 commit comments

Comments
 (0)