Skip to content

Commit ab62614

Browse files
committed
Remove 5.x series deprecations and introductions
1 parent 54dc59f commit ab62614

File tree

1 file changed

+9
-50
lines changed

1 file changed

+9
-50
lines changed

modules/ROOT/pages/clustering/databases.adoc

Lines changed: 9 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -468,11 +468,11 @@ SHOW DATABASE foo;
468468
=== Seed from URI
469469

470470
This method seeds all servers with an identical seed from an external source, specified by the URI.
471-
The seed can either be a full backup, a differential backup (xref:clustering/databases.adoc#cloud-seed-provider[`CloudSeedProvider`], introduced in Neo4j 5.26), or a dump from an existing database.
471+
The seed can either be a full backup, a differential backup, or a dump from an existing database.
472472
The sources of seeds are called _seed providers_.
473473

474474
The mechanism is pluggable, allowing new sources of seeds to be supported (see link:https://www.neo4j.com/docs/java-reference/current/extending-neo4j/project-setup/#extending-neo4j-plugin-seed-provider[Java Reference -> Implement custom seed providers] for more information).
475-
The product has built-in support for seed from a mounted file system (file), FTP server, HTTP/HTTPS server, Amazon S3, Google Cloud Storage (from Neo4j 5.25), and Azure Cloud Storage (from Neo4j 5.25).
475+
The product has built-in support for seed from a mounted file system (file), FTP server, HTTP/HTTPS server, Amazon S3, Google Cloud Storage, and Azure Cloud Storage.
476476

477477
[NOTE]
478478
====
@@ -504,7 +504,7 @@ To determine the cause of the problem, it is recommended to look at the `debug.l
504504
[[file-seed-provider]]
505505
==== FileSeedProvider
506506

507-
label:new[Introduced in 5.26], the `FileSeedProvider` supports:
507+
The `FileSeedProvider` supports:
508508

509509
** `file:`
510510

@@ -513,21 +513,20 @@ label:new[Introduced in 5.26], the `FileSeedProvider` supports:
513513

514514
The `URLConnectionSeedProvider` supports the following:
515515

516-
** `file:` label:deprecated[Deprecated in 5.26]
517516
** `ftp:`
518517
** `http:`
519518
** `https:`
520519

521520
[[cloud-seed-provider]]
522521
==== CloudSeedProvider
523522

524-
label:new[Introduced in 5.25], the `CloudSeedProvider` supports:
523+
The `CloudSeedProvider` supports:
525524

526525
** `s3:`
527526
** `gs:`
528527
** `azb:`
529528

530-
Starting from Neo4j 5.26, the `CloudSeedProvider` supports using xref:backup-restore/modes.adoc#differential-backup[differential backup] files as seeds.
529+
The `CloudSeedProvider` supports using xref:backup-restore/modes.adoc#differential-backup[differential backup] files as seeds.
531530
With the provided differential backup file, the `CloudSeedProvider` searches the directory containing differential backup files for a xref:backup-restore/online-backup.adoc#backup-chain[backup chain] ending at the specified differential backup, and then seeds using this backup chain.
532531

533532
[.tabbed-example]
@@ -573,44 +572,6 @@ CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 'azb://myStorageAcco
573572
======
574573
=====
575574

576-
[[s3-seed-provider]]
577-
==== S3SeedProvider
578-
579-
The `S3SeedProvider` supports:
580-
581-
** `s3:` label:deprecated[Deprecated in 5.26]
582-
583-
584-
[NOTE]
585-
====
586-
Neo4j 5 comes bundled with necessary libraries for AWS S3 connectivity.
587-
Therefore, if you use `S3SeedProvider`,`aws cli` is not required but can be used with the `CloudSeedProvider`.
588-
====
589-
590-
The `S3SeedProvider` requires additional configuration.
591-
This is specified with the `seedConfig` option.
592-
This option expects a comma-separated list of configurations.
593-
Each configuration value is specified as a name followed by `=` and the value, as such:
594-
595-
[source, cypher, role="noplay"]
596-
----
597-
CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 's3:/myBucket/myBackup.backup', seedConfig: 'region=eu-west-1' }
598-
----
599-
600-
`S3SeedProvider` also requires passing in credentials.
601-
These are specified with the `seedCredentials` option.
602-
Seed credentials are securely passed from the Cypher command to each server hosting the database.
603-
For this to work, Neo4j on each server in the cluster must be configured with identical keystores.
604-
This is identical to the configuration required by remote aliases, see xref:database-administration/aliases/remote-database-alias-configuration.adoc#remote-alias-config-DBMS_admin-A[Configuration of DBMS with remote database alias].
605-
If this configuration is not performed, the `seedCredentials` option fails.
606-
607-
[source, cypher, role="noplay"]
608-
----
609-
CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 's3:/myBucket/myBackup.backup', seedConfig: 'region=eu-west-1', seedCredentials: [accessKey];[secretKey] }
610-
----
611-
Where `accessKey` and `secretKey` are provided by AWS.
612-
613-
614575
==== Seed provider reference
615576

616577
[cols="1,2,2",options="header"]
@@ -620,8 +581,7 @@ Where `accessKey` and `secretKey` are provided by AWS.
620581
| URI example
621582

622583
| `file:`
623-
| `URLConnectionSeedProvider` label:deprecated[Deprecated in 5.26], +
624-
`FileSeedProvider` label:new[Introduced in 5.26]
584+
| `FileSeedProvider`
625585
| `file:/tmp/backup1.backup`
626586

627587
| `ftp:`
@@ -637,16 +597,15 @@ Where `accessKey` and `secretKey` are provided by AWS.
637597
| `\https://myhttp.com/backups/backup1.backup`
638598

639599
| `s3:`
640-
| `S3SeedProvider` label:deprecated[Deprecated in 5.26], +
641-
`CloudSeedProvider` label:new[Introduced in 5.25]
600+
| `CloudSeedProvider`
642601
| `s3://mybucket/backups/backup1.backup`
643602

644603
| `gs:`
645-
| `CloudSeedProvider` label:new[Introduced in 5.25]
604+
| `CloudSeedProvider`
646605
| `gs://mybucket/backups/backup1.backup`
647606

648607
| `azb:`
649-
| `CloudSeedProvider` label:new[Introduced in 5.25]
608+
| `CloudSeedProvider`
650609
| `azb://mystorageaccount.blob/backupscontainer/backup1.backup`
651610
|===
652611

0 commit comments

Comments
 (0)