Details
-
New Feature
-
Status: Resolved
-
Minor
-
Resolution: Invalid
-
3.14.0
-
None
-
None
-
Unknown
Description
I am trying to use camel-quartz in a clustered setup where the possibility of using a DBStore for managing execution is not available. I am looking for a mechanism to intercept the execution within the CamelJob to skip the execution/ creation of exchange if the trigger was handled on another cluster instance. Existing documentation and codebase do not seem to provide such a mechanism. Can there be a mechanism to allow a custom check to skip execution before the trigger? One the consumer can contribute.