You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some way (python, shell, ect. script) to automatically update my APOC.core & APOC.extended jars to match the version of Neo4j server installed.
It doesn't have to be fully automatic (ie lights-out, no interaction), but at least automatable (ie I can schedule or keep everything in sync when one is updated).
Considered alternatives
Right now Neo4j-Sever can be automated, but APOC.core & APOC.extended as completely done MANUALLY. This leads to all sorts of pain and trouble because in our DEV environment the server is auto-updated by the system (RHEL "dnf" package manager) so I don't always know when an update has occurred. They (APOC.* and Neo4j-Sever) are frequently out-of-sync
How this feature can improve the project?
Reduce headaches for admins. Right now it's a manual, disjointed process but requires versions be exactly paired. The distribution of the Neo4j server and the associated APOC.core & APOC.extended are completely independent. This leads to a TON of babysitting, troubleshooting, and gnashing of teeth when they are out of sync (which happens quite often).
The text was updated successfully, but these errors were encountered:
Hello @numericOverflow, APOC Core is currently in maintenance mode and does not accept feature requests currently. If you would like to have your request considered please submit your request to the APOC extended repo instead.
Guidelines
Feature description (Mandatory)
Some way (python, shell, ect. script) to automatically update my APOC.core & APOC.extended jars to match the version of Neo4j server installed.
It doesn't have to be fully automatic (ie lights-out, no interaction), but at least automatable (ie I can schedule or keep everything in sync when one is updated).
Considered alternatives
Right now Neo4j-Sever can be automated, but APOC.core & APOC.extended as completely done MANUALLY. This leads to all sorts of pain and trouble because in our DEV environment the server is auto-updated by the system (RHEL "dnf" package manager) so I don't always know when an update has occurred. They (APOC.* and Neo4j-Sever) are frequently out-of-sync
How this feature can improve the project?
Reduce headaches for admins. Right now it's a manual, disjointed process but requires versions be exactly paired. The distribution of the Neo4j server and the associated APOC.core & APOC.extended are completely independent. This leads to a TON of babysitting, troubleshooting, and gnashing of teeth when they are out of sync (which happens quite often).
The text was updated successfully, but these errors were encountered: