This is an automated email from the ASF dual-hosted git repository.
oscerd 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 bdac771f3f82 CAMEL-23575: docs - sync camel-mongodb-gridfs 4.14
upgrade-guide entry to main (#23487)
bdac771f3f82 is described below
commit bdac771f3f8211d8fcede485b248deb566166b6a
Author: Andrea Cosentino <[email protected]>
AuthorDate: Mon May 25 09:57:48 2026 +0200
CAMEL-23575: docs - sync camel-mongodb-gridfs 4.14 upgrade-guide entry to
main (#23487)
Adds the camel-mongodb-gridfs header-constant rename note to the
"Upgrading from 4.14.3 to 4.14.8" section of
camel-4x-upgrade-guide-4_14.adoc
on main, matching the backport to camel-4.14.x (#23486, cherry-pick of
#23413 / CAMEL-23575). Marked "- potential breaking change" for
consistency with the neighbouring camel-jira / camel-cxf / camel-jgroups
entries in the same release section (CAMEL-23577 sweep convention).
Per the backport upgrade-guide policy, the version-specific upgrade-guide
files for all releases live on main as the canonical history; the entry
for the 4.14.8 release line must therefore be present here even though
the code fix is backported to the camel-4.14.x maintenance branch.
Reported by Claude Code on behalf of Andrea Cosentino.
---
.../ROOT/pages/camel-4x-upgrade-guide-4_14.adoc | 25 ++++++++++++++++++++++
1 file changed, 25 insertions(+)
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
index 8b8d763101f6..61e538bb690a 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
@@ -262,6 +262,31 @@ As a consequence, the generated Endpoint DSL header
accessors on
* `linkType()` -> `jiraLinkType()`
* `minutesSpent()` -> `jiraMinutesSpent()`
+=== camel-mongodb-gridfs - potential breaking change
+
+The Exchange header values exposed by `GridFsConstants` have been renamed to
follow the standard
+Camel naming convention, bringing `camel-mongodb-gridfs` in line with the
parent `camel-mongodb`
+component (`MongoDbConstants.OPERATION_HEADER = "CamelMongoDbOperation"`). The
Java field names
+are unchanged, so routes referencing the constants symbolically
+(e.g. `GridFsConstants.GRIDFS_OPERATION`, `GridFsConstants.GRIDFS_OBJECT_ID`)
continue to work
+without modification. However, routes that set or read these headers using the
raw string values
+must be updated:
+
+* `gridfs.operation` -> `CamelGridFsOperation`
+* `gridfs.metadata` -> `CamelGridFsMetadata`
+* `gridfs.chunksize` -> `CamelGridFsChunkSize`
+* `gridfs.objectid` -> `CamelGridFsObjectId`
+* `gridfs.fileid` -> `CamelGridFsFileId`
+
+As a consequence, the generated Endpoint DSL header accessors on
`GridFsHeaderNameBuilder`
+have been renamed accordingly:
+
+* `gridfsOperation()` -> `gridFsOperation()`
+* `gridfsMetadata()` -> `gridFsMetadata()`
+* `gridfsChunksize()` -> `gridFsChunkSize()`
+* `gridfsObjectid()` -> `gridFsObjectId()`
+* `gridfsFileid()` -> `gridFsFileId()`
+
== Upgrading from 4.14.2 to 4.14.3
=== camel-tika
