Releases: kagkarlsson/db-scheduler
Releases · kagkarlsson/db-scheduler
9.1
9.0
- PR #154 fixes bug described in #146. The Scheduler was interfering with externally managed transactions by calling explicit commit when autocommit was set to false. This bug was introduced in v7.1. For anyone using Spring to manage transactions, it is highly recommended to upgrade.
- PR #153 avoids running default
AutodetectJdbcCustomization
whenJdbcCustomization
is overridden - PR #149 adds tests validating db-scheduler is compatible with Java 15. Contributions by evenh.
8.2
- PR #139 adds
FixedDelay.ofMillis(millis)
. Contributions by evenh. - PR #142 adds javadoc for
SchedulerClient
. Contributions by cunhazera - PR #143 fixes Spring deprecation (
Health[Indicator -> Contributor]AutoConfiguration
). Contributions by evenh. - PR #144 migrates db-scheduler CI from Travis to Github Actions. Contributions by evenh.
- PR #138 makes
Scheduler
graceful shutdown wait configurable from the default 30m.
8.1
Version 8.1
- Provide sources for shaded dependency
com.cronutils
8.0
Version 8.0
- PR #136 introduces a new feature where changes to the
Schedule
for
aRecurringTask
is detected by the Scheduler on startup. Any existing execution is rescheduled to the new next execution-time
according to the newSchedule
.
Note: ASchedule
must now indicate whether it is deterministic or not (i.e. if it will evaluate to the same instants). - PR #134 fixes some edge-cases (that were fairly likely for
high-throughput cases) that caused the Scheduler to stop fetching further batches of due executions until next pollInterval. - PR #132 fixes race-condition for immediate-execution that may cause
the execution to be "missed" until next pollingInterval. - PR #131 upgrades guava to 29.0.
- PR #129 adjusts defaults for Spring Boot to match
SchedulerBuilder
.
Contributions by evenh.
7.2
7.1
7.0
Version 7.0
- PR #105 fixes bug for
Microsoft Sql Server
where incorrect timezone handling caused persisted instant != read instant.
This bug was discovered when adding testcontainers-based compatibility tests and has strangely enough never been reported by users. So this release will cause a change
in behavior for users where the database is discovered to beMicrosoft SQL Server
.