[
https://issues.apache.org/jira/browse/CAMEL-19590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasanth Ganesh Rao updated CAMEL-19590:
----------------------------------------
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. (was: 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 before the trigger?)
> camel-quartz: Skip execution on custom conditions
> -------------------------------------------------
>
> Key: CAMEL-19590
> URL: https://issues.apache.org/jira/browse/CAMEL-19590
> Project: Camel
> Issue Type: New Feature
> Components: camel-quartz
> Affects Versions: 3.14.0
> Reporter: Prasanth Ganesh Rao
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
