Add native support for CronJobs #1197
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #1182
This add support for cron jobs in the following components:
quartz,timer,cron.The cron component can already be used, even if not present in Camel 3.0.x, as long as it is materialized into a CronJob. When
cronis used and the cron expression is not compatible with Kubernetes CronJobs, it will fallback to using quartz automatically (but this requires Camel 3.1.x to work).Timer and Quartz work oob. When a route is using e.g.
timer:tick?period=1mit's translated into a cron expression.Release Note