Safe process for recreating database after a incremental import #2704
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tinwelint
requested changes
Nov 11, 2025
modules/ROOT/pages/import.adoc
Outdated
| * Import performance is important because you have a large amount of data (millions/billions of entities). | ||
| * The database can be taken offline and you have direct access to one of the servers hosting your Neo4j DBMS. | ||
| * The database is either empty or its content is unchanged since a previous incremental import. | ||
| * The database is either empty. |
Member
There was a problem hiding this comment.
This no longer looks like a proper sentence. For the removed incremental import part here are the constraints that apply:
- database is stopped and an incremental import is run from start to end, or
- database is stopped,
preparestep of incremental import is run. Database can potentially be started in read-only mode whilebuildstep of incremental import is run and then finally the database is stopped whilemergestep of incremental is run. To run the stepsprepare,buildandmergesplit like that with taking the db online/offline is a bit complicated so I can't imagine many users doing this, if any.
Also, feel free to rephrase this however you want, if you'd want any of this information in here.
NataliaIvakina
force-pushed
the
control-351-incremental-import-followed-by-recreate-database
branch
from
6a2a9f6 to
2d7bb60
Compare
jackwaudby
commented
Nov 18, 2025
Collaborator
|
This PR includes documentation updates Updated pages: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes CONTROL-351