Skip to content

CAMEL-24000: camel-spring-boot - upgrade guide entry for Duration configuration properties #24593

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Croway merged 1 commit into from
Jul 10, 2026
Merged

CAMEL-24000: camel-spring-boot - upgrade guide entry for Duration configuration properties #24593

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -296,3 +296,28 @@ Four new operations have been added to the Weaviate component, leveraging v6 cli
* `HYBRID_QUERY` — Keyword + vector hybrid search. The exchange body is the query text (`String`). Supports `CamelWeaviateQueryTopK` (default 10), `CamelWeaviateHybridAlpha` (0.0 = pure BM25, 1.0 = pure vector), `CamelWeaviateQueryVector` (optional pre-computed vector to override server-side vectorizer), and `CamelWeaviateFields` headers. Returns a `QueryResponse<Map<String, Object>>`.
* `BM25_QUERY` — Keyword-only (BM25) search. The exchange body is the query text (`String`). Supports `CamelWeaviateQueryTopK` and `CamelWeaviateFields` headers. Returns a `QueryResponse<Map<String, Object>>`.
* `AGGREGATE` — Returns aggregate statistics for a collection. No body required. Returns an `AggregateResponse` with `totalCount()` and per-property aggregations.

=== camel-spring-boot - Duration configuration properties

The following configuration properties are now bound as `java.time.Duration` instead of raw
milliseconds (`long`/`int`):

* `camel.routecontroller.initial-delay`
* `camel.routecontroller.back-off-delay`
* `camel.routecontroller.back-off-max-delay`
* `camel.routecontroller.back-off-max-elapsed-time`
* `camel.startupcondition.interval`
* `camel.startupcondition.timeout`

Plain numeric values in `application.properties`/`application.yaml` are still interpreted as
milliseconds, so existing configurations keep working unchanged. In addition, readable duration
values such as `5s` or `2m` are now supported.

This is a source-incompatible change for code that reads these values programmatically: the
getters and setters of `SupervisingRouteControllerConfiguration` and
`CamelStartupConditionConfigurationProperties` now use `java.time.Duration` instead of
`long`/`int`.

The clustered route controller property `camel.clustered.controller.initial-delay` is unchanged:
it keeps its `String` type because it supports Camel time patterns (for example `10 seconds`)
that `Duration` binding does not.