Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

StoreCopyFiltered #63

Open
wants to merge 2 commits into
base: 3.5
Choose a base branch
from

Conversation

Mahmoud-kamal12
Copy link

Neo4j Store Copy Tool - Release Description 🚀

📌 Overview

The Neo4j Store Copy Tool is a high-performance, optimized script designed to copy specific data from a Neo4j 3.5 database into a new database. This tool allows for filtered node copying based on org_id, ensuring only relevant data is transferred while preserving relationships.

The tool is optimized for fast execution on high-memory servers (30GB RAM or more) and supports both Community and Enterprise editions of Neo4j.


🔥 Key Features

Selective Data Copying – Copies only nodes and relationships for a specific org_id.
High Performance – Optimized for servers with large RAM, using custom heap and caching settings.
Preserves Node IDs – Ensures relationships remain intact after migration.
Supports Large Databases – Uses batch processing for scalability.
Automated Execution – Can be run immediately after deployment with minimal configuration.
Flexible Deployment – Packaged as a standalone script with all dependencies included.


🛠 System Requirements

  • Neo4j 3.5 Community or Enterprise Edition
  • Java 8 or 11
  • Linux-based server (Ubuntu, CentOS, RHEL, or Debian recommended)
  • At least 16GB RAM (Optimized for 30GB RAM servers)

🚀 Installation & Deployment

1️⃣ Install Java (if not already installed)

sudo apt update  
sudo apt install openjdk-11-jre -y  

2️⃣ Extract the Tool Package

tar -xzvf neo4j-copy-tool.tar.gz  
cd neo4j-copy-tool/  
chmod +x copy-store-filtered.sh  

3️⃣ Run the Script

./copy-store-filtered.sh community source.db target.db 123  

📌 Replace:

  • community → Neo4j Edition (enterprise if using Enterprise version).
  • source.db → Path to the source database.
  • target.db → Path to the target database.
  • 123 → The org_id of the data to be copied.

Performance Optimization

  • Heap Memory: Configurable (default: 10G).
  • Page Cache: Uses 16GB for optimal performance.
  • Batch Processing: Ensures high-speed migration without overloading memory.

📜 License & Usage

This tool is provided as-is under an open-source license. Contributions and improvements are welcome!

📩 For support & updates, contact: [Your Contact Info]

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant