Closed conker84 closed 2 years ago
@conker84 @fbiville @JMHReif @jexp
Hi, I've just stumbled against this issue.
After setting a trigger in my local environment, I failed to deploy this feature to the neo4j cluster environment, and realized that only the system leader allows for apoc.trigger.add
when my db leader is on another node.
I wish the documentation mentioned that triggers aren't yet supported on clusters. What are the couple of options available ? Is there anything I can do to get triggers to work in my cluster and not throw away all the work involving neo4j triggers I'm trying to release ?
Running neo4j 4.1 on the GCP marketpace neo4j enterprise causal cluster. Thank you for your support
Edit: As a temporary solution, I removed the core replicas, replacing them with one standalone leader and read replicas.
Related to (#2193) in a cluster env the
systemdb
can have aLEADER
in a different instance where the actualcall apoc.trigger.add
happened.We have a couple of options here but I need to discuss them with @fbiville @JMHReif & @jexp