This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/main by this push:
     new 287dc5192903 CAMEL-26923: camel-duckdb - upgrade guide note for the 
copy operation in 4.22.3 (#30160)
287dc5192903 is described below

commit 287dc519290340101e26cf26ebca8a66330ac37d
Author: Claus Ibsen <[email protected]>
AuthorDate: Mon Nov 16 14:33:56 2026 +0100

    CAMEL-26923: camel-duckdb - upgrade guide note for the copy operation in 
4.22.3 (#30160)
    
    The upgrade guides of all release lines live on `main`. This PR adds the 
note for the `camel-4.22.x` backport of
    #29844 (camel-duckdb: copy loads one local file unless options allow URLs 
or globs) to
    `camel-4x-upgrade-guide-4_22.adoc`, in the section "Upgrading from 4.22.2 
to 4.22.3":
    
    - **camel-duckdb - copy loads one local file unless allowUrlCopySource or 
allowGlobCopySource is set**: a `copy`
      source with a URL scheme or glob pattern characters now fails unless the 
new `allowUrlCopySource=true` or
      `allowGlobCopySource=true` option is set, and the new `copyBaseDirectory` 
option sets the directory a local source
      must be inside.
    
    _Claude Code on behalf of davsclaus_
    
    Co-Authored-By: Claude Opus 5.5 <[email protected]>
---
 .../modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc      | 12 ++++++++++++
 1 file changed, 12 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 2b1de60e6ac8..9132e46f0b7b 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
@@ -98,6 +98,18 @@ configurations are not affected.
 The webhook consumer still logs the body it validates at `DEBUG`, but no 
longer the signature from the `X-Signature` header, nor the signature it 
calculates.
 The `InvalidMessageSignatureException` of a failed check no longer carries the 
calculated signature: `getCalculatedSignature()` returns `null` and is 
deprecated, as is the constructor that takes it.
 
+=== camel-duckdb - copy loads one local file unless allowUrlCopySource or 
allowGlobCopySource is set
+
+The `copy` operation of the `duckdb` producer gave the path from the message 
body to DuckDB as it was, so DuckDB read a
+value with a URL scheme (such as `https://` or `s3://`) as a remote file, and 
expanded a value with glob pattern
+characters (`*`, `?`, `[` or `{`) to all the matching files. Now `copy` loads 
a single local file by default, and a
+source with a URL scheme or glob pattern characters fails with an 
`IllegalArgumentException`. This also applies to a
+`File` body, such as a file from the `file` consumer, whose name has one of 
these characters. A route that loads such
+sources must set the new `allowUrlCopySource=true` or 
`allowGlobCopySource=true` option (both disabled by default).
+
+The new `copyBaseDirectory` option sets the directory that a local source must 
be inside, after resolving symbolic
+links.
+
 === camel-file - idempotent consumer with an idempotent read lock
 
 With `idempotent=true` (or `noop=true`) and `readLock=idempotent`, 
`idempotent-changed` or `idempotent-rename`, the

Reply via email to