This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch docs/CAMEL-24539-upgrade-guide-4_22-sync in repository https://gitbox.apache.org/repos/asf/camel.git
commit b669885375497aaaf0db49eace2a3b760415f32e Author: Claus Ibsen <[email protected]> AuthorDate: Sat Sep 12 09:24:32 2026 +0200 CAMEL-24539: docs - add the camel-openai note to the 4.22.1 upgrade guide The change landed on camel-4.22.x in #26347, so 4.22.1 is the first release to carry it, but on main the note only exists in camel-4x-upgrade-guide-4_23.adoc. The 4_XX guides on main are the canonical history across all release lines, so 4_22.adoc was left out of sync with what 4.22.1 actually ships. The wording matches the branch rather than 4_23.adoc: the moderation and image operations do not exist on 4.22.x, so they are not listed as unchanged. The 4_23.adoc entry is left in place - every other 4.22.1 entry appears in both guides. Also adds the missing blank line before three section headings in the same file (camel-dynamic-router, camel-sql and the 4.21-to-4.22 heading). AsciiDoc only recognises a heading at the start of a block, so without it the heading is absorbed into the preceding paragraph. Signed-off-by: Claus Ibsen <[email protected]> Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Signed-off-by: Claus Ibsen <[email protected]> --- .../modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc index c8c256ffd439..565d85c70ada 100644 --- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc +++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc @@ -42,6 +42,7 @@ It is unset by default, which keeps the previous behaviour of accepting any path Additionally, a local input path that does not exist is now reported as a `File not found` `IOException` before Docling is invoked. Previously the size check silently skipped a path that resolved to nothing and the failure surfaced later, from the Docling process or API call. + === camel-dynamic-router The `dynamic-router-control` endpoint no longer takes the subscription `predicate`, or the @@ -219,6 +220,21 @@ Documents carrying an internal DTD subset still parse. To restore the previous behaviour and allow external entity resolution, set the new `allowExternalEntities` option to `true` on the data format or on the endpoint (`smooks:config.xml?allowExternalEntities=true`). + +=== camel-openai + +When `storeFullResponse=true`, the embeddings and audio operations now store their full SDK response +under an operation-specific exchange property instead of the chat-completion property `CamelOpenAIResponse`. +That property is typed as the chat-completion response (`com.openai.models.chat.completions.ChatCompletion`), +so a downstream reader that expected that type received an incompatible object. + +* embeddings now use `CamelOpenAIEmbeddingsResponse` (`com.openai.models.embeddings.CreateEmbeddingResponse`). +* audio transcription now uses `CamelOpenAIAudioTranscriptionResponse` (`com.openai.models.audio.transcriptions.TranscriptionCreateResponse`). +* audio translation now uses `CamelOpenAIAudioTranslationResponse` (`com.openai.models.audio.translations.TranslationCreateResponse`). + +A route that reads the full embeddings or audio response from `CamelOpenAIResponse` must switch to the +matching property. The chat-completion and responses operations are unchanged. + == Upgrading Camel 4.21 to 4.22 === camel-tika @@ -1360,6 +1376,7 @@ on the bytes of a non-ASCII payload and make verification fail. already UTF-8 (JEP 400), so this is a no-op there; on Java 17 with a non-UTF-8 default, the signature of a non-ASCII `String` payload changes. Binary bodies (`byte[]`, `InputStream`) are unaffected, as they are signed byte-for-byte. + === camel-sql - Schema-qualified aggregation repository names The table-name validation in `JdbcAggregationRepository` now accepts schema-qualified names
