Disable custom procedure check by default

[umuzammil]

APOC custom procedures feature periodically checks for updated custom procedures. This process e.g. does a call to db.clearQueryCaches.

Perhaps we can re-evaluate if we really need to do this and/or be if we should switch off this feature based on a config option for users that don't use custom cypher procedures.

We don't get any flag set e.g. in cluster when procedures do change. Maybe we could store a int number in systemdb and increment that upon every change to a cypher procedure. All cluster members check if that sequence number has changed if so, they update themselves.

The periodic check can perhaps be explicitly enabled via a config option.

[conker84]

As agreed with @umuzammil and the customer the issue is fixed in the last APOC release.
Feel free to reopen if you need

[umuzammil]

thanks @conker84 .. the issue wasn't encountered in APOC 4.0.0.4, however the particular request is to re-evaluate if we should switch off custom procedure checks upon startup, by default or based on a config option for users that don't use custom cypher procedures.

[umuzammil]

Hello,

Please re-open this, since the aim here is to re-evaluate if we really need to run custom procedure checks and/or be if we should switch off this feature based on a config option for users that don't use custom cypher procedures.

We don't get any flag set e.g. in cluster when procedures do change. Maybe we could store a int number in systemdb and increment that upon every change to a cypher procedure. All cluster members check if that sequence number has changed if so, they update themselves.

The periodic check can perhaps be explicitly enabled via a config option.