@@ -129,41 +129,6 @@ CREATE DATABASE foo OPTIONS { seedURI: 'azb://myStorageAccount/myContainer/myBac
129129=====
130130
131131
132- ==== Support for seeding up to a date or a transaction ID
133-
134- Starting from Neo4j 2025.01, the `CloudSeedProvider` supports seeding up to a specific date or transaction ID using the `seedRestoreUntil` option.
135-
136- [role=label--new-2025.01]
137- Seed up to a specific date::
138-
139- To seed up to a specific date, provide the differential backup containing the data up to that date.
140- +
141- [source,cypher]
142- ----
143- CREATE DATABASE foo OPTIONS {
144- seedURI: 's3://myBucket/myBackup.backup',
145- seedRestoreUntil: datetime('2019-06-01T18:40:32.142+0100')
146- }
147- ----
148- +
149- This will seed the database with transactions committed before the provided timestamp.
150-
151- [role=label--new-2025.01]
152- Seed up to a specific transaction ID::
153-
154- To seed up to a specific transaction ID, provide the differential backup containing the data up to that transaction ID.
155- +
156- [source,cypher]
157- ----
158- CREATE DATABASE foo OPTIONS {
159- seedURI: 's3://myBucket/myBackup.backup',
160- seedRestoreUntil: 123
161- }
162- ----
163- +
164- This will seed the database with transactions up to (but not including) transaction 123.
165-
166-
167132[role=label--deprecated]
168133[[s3-seed-provider]]
169134=== S3SeedProvider
@@ -172,7 +137,7 @@ This will seed the database with transactions up to (but not including) transact
172137
173138The `S3SeedProvider` supports:
174139
175- ** `s3:` label:deprecated[Deprecated in 5.26]
140+ ** `s3:`
176141
177142
178143[NOTE]
@@ -248,3 +213,36 @@ Where `<accessKey>` and `<secretKey>` are provided by AWS.
248213| `CloudSeedProvider`
249214| `azb://mystorageaccount.blob/backupscontainer/backup1.backup`
250215|===
216+
217+
218+ [[seed-restore-until-option]]
219+ == Support for seeding up to a date or a transaction ID
220+
221+ Starting from Neo4j 2025.01, when creating a database you can seed up to a specific date or transaction ID via the `seedRestoreUntil` option.
222+
223+ The `seedRestoreUntil` option is supported by the `CloudSeedProvider` and the `FileSeedProvider`.
224+
225+
226+ Seed up to a specific date::
227+
228+ To seed up to a specific date, you need to pass the differential backup, which contains the data up to that date.
229+ +
230+ [source,shell]
231+ ----
232+ CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 's3://myBucket/myBackup.backup', seedRestoreUntil: datetime("2019-06-01T18:40:32.142+0100") }
233+ ----
234+ +
235+ This will seed the database with transactions committed before the provided timestamp.
236+
237+
238+ Seed up to a specific transaction ID::
239+
240+ To seed up to a specific transaction ID, you need to pass the differential backup that contains the data up to that transaction ID.
241+ +
242+ [source,shell]
243+ ----
244+ CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 's3://myBucket/myBackup.backup', seedRestoreUntil: 123 }
245+ ----
246+ +
247+ This will seed the database with transactions up to, but not including transaction 123.
248+
0 commit comments