Custom Patch Order / Relese process (DEV --> Quality --> PROD)
under review
Aberham, Josef (IT DA DO PL)
It would be good to have a custom Release or Patch Process. Patches should be installed in a specific order with delay between instances of some weeks.
Patch Order: (DEV Instance --> Quality-Instance --> PROD).
But in a production, it could be very critical. A Patch was crashing our application. This apoc was not more working after the patch: Apoc.periodic.iterate is throwing null pointer exception in AURA DB with Neo4j 5.18.0
(see Ticket 00030116)
Aman Singh
Merged in a post:
Configure maintenance window
Ron van Weverwijk
Neo4j aura is continuously upgrading to the latest and greatest version. This is very useful, but not during "office times". We encountered issues for our end users at the moment of an upgrade. For a couple of minutes, write queries where delayed.
It would be helpful to be able to configure a maintenance window where these upgrades can happen (including timezone).
Next to that it would be good to know if upgrades are going to happen and/or when there have been applied. Last time I needed to create a support task to find the root cause of the issue mentioned above. Being able to know the history of the cluster would save time from the support team.
Paul Blewett
under review
Thank you for raising this Josef, we're sorry you've been impacted in this way and we will begin a review on this with the team.
Ron van Weverwijk
I completely agree. We also had production problems, by a difference in property handling in Cypher. Releases at the moment are not announced, changes are unknown for us as endusers. Currently release strategy is really unacceptable in my opinion!
James Ontiveros
We have experienced similar troubles, and this would be very helpful!
John Kennedy
Thanks for the level of detail on this request Ron van Weverwijk, it's extremely helpful.
John