Skip to content

Commit 8d2bfc7

Browse files
committed
Deprecate existingDataSeedInstance option to CREATE DATABASE
Replace with new option `existingDataSeedServer`
1 parent c46212c commit 8d2bfc7

File tree

2 files changed

+9
-6
lines changed

2 files changed

+9
-6
lines changed

modules/ROOT/pages/clustering/databases.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -284,7 +284,7 @@ See <<#_create_database, `CREATE DATABASE`>> for more information.
284284
----
285285
CREATE DATABASE foo
286286
TOPOLOGY [desired number of primaries] PRIMARIES [desired number of secondaries] SECONDARIES
287-
OPTIONS {existingData: 'use', existingDataSeedInstance: '8512c9b9-d9e8-48e6-b037-b15b0004ca18'};
287+
OPTIONS {existingData: 'use', existingDataSeedServer: '8512c9b9-d9e8-48e6-b037-b15b0004ca18'};
288288
----
289289
. Verify that the `foo` database is online on the desired number of servers, in the desired roles.
290290
If the `foo` database is of considerable size, the execution of the command can take some time.

modules/ROOT/pages/database-administration/standard-databases/create-databases.adoc

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -76,13 +76,16 @@ The `CREATE DATABASE` command can have a map of options, e.g. `OPTIONS {key: 'va
7676
| `use`
7777
|
7878
Controls how the system handles existing data on disk when creating the database.
79-
Currently, this is only supported with `existingDataSeedInstance` and `seedURI`, and must be set to `use`, which indicates the existing data files should be used for the new database.
79+
Currently, this is only supported with `existingDataSeedInstance`, `existingDataSeedServer` and `seedURI`, and must be set to `use`, which indicates the existing data files should be used for the new database.
8080

81-
| `existingDataSeedInstance`
81+
82+
|`existingDataSeedServer` label:new[new in 5.25]
83+
84+
`existingDataSeedInstance` label:deprecated[deprecated in 5.25]
8285
| ID of the cluster server
8386
|
8487
Defines which server is used for seeding the data of the created database.
85-
The server ID can be found in the `serverId` column after running `SHOW SERVERS`.
88+
The server ID can be found in the `serverId` column after running `SHOW SERVERS`. `existingDataSeedInstance` was replaced by `existingDataSeedServer` in Neo4j 5.25.
8689

8790
| `seedURI`
8891
| URI to a backup or a dump from an existing database.
@@ -110,12 +113,12 @@ For details about enrichment mode, see link:{neo4j-docs-base-uri}/cdc/current/ge
110113
| `aligned` \| `standard` \| `high_limit` \| `block`
111114
|
112115
Defines the store format if the database created is new.
113-
If the store is seeded with `seedURI` or `existingDataSeedInstance`, or if the command is being used to mount pre-existing store files already present on the disk, they will use their current store format without any alterations.
116+
If the store is seeded with `seedURI`, `existingDataSeedInstance` or `existingDataSeedServer`, or if the command is being used to mount pre-existing store files already present on the disk, they will use their current store format without any alterations.
114117
|===
115118

116119
[NOTE]
117120
====
118-
The `existingData`, `existingDataSeedInstance`, `seedURI`, `seedConfig`, and `seedCredentials` options cannot be combined with the `OR REPLACE` part of this command.
121+
The `existingData`, `existingDataSeedInstance`, `existingDataSeedServer`, `seedURI`, `seedConfig`, and `seedCredentials` options cannot be combined with the `OR REPLACE` part of this command.
119122
More details about seeding options can be found in xref::clustering/databases.adoc#cluster-seed[Seed a cluster].
120123
====
121124

0 commit comments

Comments
 (0)