apoc.trigger.start
Procedure
apoc.trigger.start(databaseName String, name String)
- eventually restarts the given paused trigger.
Signature
apoc.trigger.start(databaseName :: STRING?, name :: STRING?) :: (name :: STRING?, query :: STRING?, selector :: MAP?, params :: MAP?, installed :: BOOLEAN?, paused :: BOOLEAN?)
Output parameters
Name | Type |
---|---|
name |
STRING? |
query |
STRING? |
selector |
MAP? |
params |
MAP? |
installed |
BOOLEAN? |
paused |
BOOLEAN? |
Enable Triggers
By default triggers are disabled.
We can enable them by setting the following property in apoc.conf
:
apoc.trigger.enabled=true
apoc.trigger.refresh=60000
Option Key | Value | Description |
---|---|---|
apoc.trigger.enabled |
true/false, default false |
Enable/Disable the feature |
apoc.trigger.refresh |
number, default 60000 |
Interval in ms after which a replication check is triggered across all cluster nodes |
Usage Examples
The There are several ways of doing this:
Moreover, the |
Installing, updating, or removing a trigger is an eventually consistent operation.
Therefore, they are not immediately added/updated/removed,
but have a refresh rate handled by the APOC configuration |
This example assumes that an apoc.trigger.install
has been executed,
and then stopped using apoc.trigger.stop
.
In this case, it is possible to restart the trigger by running the following query:
CALL apoc.trigger.start('neo4j', 'count-removals');
name | query | selector | params | installed | paused |
---|---|---|---|---|---|
"count-removals" |
{} |
{} |
TRUE |
FALSE |
Was this page helpful?