Skip to content
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

Optionally configure APOC to not store information in the system database but the current database #3040

Closed
jexp opened this issue Jul 7, 2022 · 3 comments
Assignees
Labels
core-functionality Adding new procedure, function or signature to APOC core

Comments

@jexp
Copy link
Member

jexp commented Jul 7, 2022

We've discussed this before but I didn't create an issue for it.

Currently APOC stores information on triggers, custom procs, uuid-handler, etc. in the system database.

As an configuration option it should be possible to also store this information in the current database, which would also alleviate some of the cluster leaderships issues, but with the drawback that there would be additional nodes that don't belong to the actual graph data in the current db.

This would also cover the issues that triggers or custom procedures are deleted when a database is deleted.

@jexp
Copy link
Member Author

jexp commented Jul 7, 2022

We probably also need to provide some migration path, if apoc currently uses teh system db and the setting is changed, then it should move the information to the current db.

Need to look at what's happening with global settings that span multiple databases, perhaps write them to the neo4j database.

@vga91
Copy link
Collaborator

vga91 commented Jul 25, 2022

@vga91 vga91 added the core-functionality Adding new procedure, function or signature to APOC core label Oct 6, 2022
@jexp jexp moved this to Todo in APOC Extended Larus Dec 20, 2022
@vga91 vga91 moved this from Todo to Blocked in APOC Extended Larus Jan 24, 2023
@vga91
Copy link
Collaborator

vga91 commented Nov 22, 2024

Closed since another method was chosen to solve the system db problems with clusters
See here: neo4j/apoc#250

@vga91 vga91 closed this as completed Nov 22, 2024
@github-project-automation github-project-automation bot moved this from Blocked to Done (to cherry-pick) in APOC Extended Larus Nov 22, 2024
@vga91 vga91 moved this from Done (to cherry-pick) to Done in APOC Extended Larus Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core-functionality Adding new procedure, function or signature to APOC core
Projects
Development

No branches or pull requests

3 participants