[
https://issues.apache.org/jira/browse/CAMEL-20115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasanth Ganesh Rao updated CAMEL-20115:
----------------------------------------
Description:
The feature requirement is for the camel-quartz component to support a start
date and an end date for a specific cron. This enhancement will allow users to
set a specific time frame for the cron trigger, thereby enabling more precise
scheduling and execution of jobs.
h3. Current Behavior
Currently, Quartz's TriggerBuilder allows for the setting of a start date and
end date for a trigger. However, it appears that CronTriggerImpl does not
consider these values for scheduling. Additionally, the TriggerBuilder too does
not seem to validate these dates.
h3. Proposed Enhancement
The proposed enhancement is to enable the camel-quartz to support start and end
date values. This can be achieved by allowing the following parameters in the
URI: {_}trigger.startAt=<timeInUTCMillis>&trigger.endAt=<timeInUTCMillis>{_}.
h3. Expected Behavior
With this enhancement, the camel-quartz will be able to skip the expired
trigger based on the end date in QuartzEndpoint. It will also enable the system
to avoid triggers that occur before the start date and after the end date in
CamelJob.
h3. Use Case
This feature will support the use case where users need to schedule jobs within
a specific time frame, avoiding triggers that occur outside this specified
period.
[zulipchat camel-quartz startAt and endAt support for cron
|https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/camel-quartz.20startAt.20and.20endAt.20support.20for.20cron]
was:
The feature requirement is for the camel-quartz component to support a start
date and an end date for a specific cron. This enhancement will allow users to
set a specific time frame for the cron trigger, thereby enabling more precise
scheduling and execution of jobs.
h3. Current Behavior
Currently, Quartz's TriggerBuilder allows for the setting of a start date and
end date for a trigger. However, it appears that CronTriggerImpl does not
consider these values for scheduling. Additionally, the TriggerBuilder too does
not seem to validate these dates.
h3. Proposed Enhancement
The proposed enhancement is to enable the camel-quartz to support start and end
date values. This can be achieved by allowing the following parameters in the
URI: {_}trigger.startAt=<timeInUTCMillis>&trigger.endAt=<timeInUTCMillis>{_}.
h3. Expected Behavior
With this enhancement, the camel-quartz will be able to skip the expired
trigger based on the end date in QuartzEndpoint. It will also enable the system
to avoid triggers that occur before the start date and after the end date in
CamelJob.
h3. Use Case
This feature will support the use case where users need to schedule jobs within
a specific time frame, avoiding triggers that occur outside this specified
period.
> Support for Start and End Dates in camel-quartz
> -----------------------------------------------
>
> Key: CAMEL-20115
> URL: https://issues.apache.org/jira/browse/CAMEL-20115
> Project: Camel
> Issue Type: New Feature
> Components: camel-quartz
> Affects Versions: 3.17.0
> Reporter: Prasanth Ganesh Rao
> Priority: Major
>
> The feature requirement is for the camel-quartz component to support a start
> date and an end date for a specific cron. This enhancement will allow users
> to set a specific time frame for the cron trigger, thereby enabling more
> precise scheduling and execution of jobs.
> h3. Current Behavior
> Currently, Quartz's TriggerBuilder allows for the setting of a start date and
> end date for a trigger. However, it appears that CronTriggerImpl does not
> consider these values for scheduling. Additionally, the TriggerBuilder too
> does not seem to validate these dates.
> h3. Proposed Enhancement
> The proposed enhancement is to enable the camel-quartz to support start and
> end date values. This can be achieved by allowing the following parameters in
> the URI:
> {_}trigger.startAt=<timeInUTCMillis>&trigger.endAt=<timeInUTCMillis>{_}.
> h3. Expected Behavior
> With this enhancement, the camel-quartz will be able to skip the expired
> trigger based on the end date in QuartzEndpoint. It will also enable the
> system to avoid triggers that occur before the start date and after the end
> date in CamelJob.
> h3. Use Case
> This feature will support the use case where users need to schedule jobs
> within a specific time frame, avoiding triggers that occur outside this
> specified period.
>
> [zulipchat camel-quartz startAt and endAt support for cron
> |https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/camel-quartz.20startAt.20and.20endAt.20support.20for.20cron]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
