-
Notifications
You must be signed in to change notification settings - Fork 75
Remove useExisting
option; polish examples & page
#2287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Conversation
This PR includes documentation updates Updated pages: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added some comments, but as I said, I would ask the Clustering team to review this PR.
---- | ||
|
||
Download and validation of the seed is only performed as the new database is started. | ||
If it fails, the database is not available and it has the `statusMessage`: `Unable to start database` of the `SHOW DATABASES` command. | ||
|
||
[source, cypher, role="noplay"] | ||
[source, cypher] | ||
---- | ||
neo4j@neo4j> SHOW DATABASES; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
neo4j@neo4j> SHOW DATABASES; | |
SHOW DATABASES; | |
---- |
---- | ||
|
||
Download and validation of the seed is only performed as the new database is started. | ||
If it fails, the database is not available and it has the `statusMessage`: `Unable to start database` of the `SHOW DATABASES` command. | ||
|
||
[source, cypher, role="noplay"] | ||
[source, cypher] | ||
---- | ||
neo4j@neo4j> SHOW DATABASES; | ||
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | |
.Example output | |
[result] | |
---- | |
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ |
@@ -55,6 +55,9 @@ The `FileSeedProvider` supports: | |||
|
|||
** `file:` | |||
|
|||
[NOTE] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[NOTE] | |
[NOTE] | |
==== |
@@ -55,6 +55,9 @@ The `FileSeedProvider` supports: | |||
|
|||
** `file:` | |||
|
|||
[NOTE] | |||
Local file paths must be absolute paths. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Local file paths must be absolute paths. | |
Local file paths must be absolute paths. | |
==== |
@@ -200,7 +215,7 @@ Where `accessKey` and `secretKey` are provided by AWS. | |||
|
|||
| `file:` | |||
| `FileSeedProvider` | |||
| `\file://tmp/backup1.backup` | |||
| `\file:/tmp/backup1.backup` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps, you mean:
| `\file:/tmp/backup1.backup` | |
| `file:///tmp/backup1.backup` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, what I wrote is correct. What you wrote is also correct. Both work. I wrote that one because triple slashes are more cumbersome that single slashes.
The only thing that doesn't work is the one that's currently documented 😅
---- | ||
CREATE DATABASE foo OPTIONS {existingData: 'use', seedURI:'s3://myBucket/myBackup.backup'} | ||
CREATE DATABASE foo OPTIONS { seedURI:'s3://myBucket/myBackup.backup' } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not aware of existingData: 'use'
being deprecated and it's not documented. I would suggest that the Clustering team review this PR.
This all started with me using this feature and noticing that the documented examples triggered a warning.
Digging further into the feature and thus the docs, I took the chance to polish examples (syntax highlighting, avoid scrolling) and a few wordings.