CAMEL-23575: camel-mongodb-gridfs - align Exchange header constant names with Camel naming convention#23413
Merged
Merged
Conversation
…mes with Camel naming convention Renames the values of the Exchange header constants in GridFsConstants to follow the standard Camel<Component><Field> naming convention used across the rest of the component catalog, bringing camel-mongodb-gridfs in line with the parent camel-mongodb component (MongoDbConstants.OPERATION_HEADER = "CamelMongoDbOperation"). The Java field names are unchanged so routes/code referencing the constants symbolically continue to work as-is: gridfs.operation -> CamelGridFsOperation gridfs.metadata -> CamelGridFsMetadata gridfs.chunksize -> CamelGridFsChunkSize gridfs.objectid -> CamelGridFsObjectId gridfs.fileid -> CamelGridFsFileId The cascading rename of the auto-generated Endpoint DSL accessors on GridFsHeaderNameBuilder is included (gridfsOperation() -> gridFsOperation(), etc.) along with the regenerated component catalog. The 4.21 upgrade-guide entry documents both the constant-value rename and the DSL-accessor rename for routes using the literal string keys or the fluent builder methods. Consistent with the same alignment applied to camel-lucene (CAMEL-23509), camel-jgroups (CAMEL-23510), camel-jgroups-raft (CAMEL-23511), and camel-cxf (CAMEL-23526). Reported by Claude Code on behalf of Andrea Cosentino. Signed-off-by: Andrea Cosentino <ancosen@gmail.com>
Croway
approved these changes
May 21, 2026
Contributor
|
🌟 Thank you for your contribution to the Apache Camel project! 🌟 🐫 Apache Camel Committers, please review the following items:
|
Contributor
|
🧪 CI tested the following changed modules:
All tested modules (10 modules)
|
oscerd
added a commit
that referenced
this pull request
May 22, 2026
…mes with Camel naming convention (#23413) (#23473) Renames the values of the Exchange header constants in GridFsConstants to follow the standard Camel<Component><Field> naming convention used across the rest of the component catalog, bringing camel-mongodb-gridfs in line with the parent camel-mongodb component (MongoDbConstants.OPERATION_HEADER = "CamelMongoDbOperation"). The Java field names are unchanged so routes/code referencing the constants symbolically continue to work as-is: gridfs.operation -> CamelGridFsOperation gridfs.metadata -> CamelGridFsMetadata gridfs.chunksize -> CamelGridFsChunkSize gridfs.objectid -> CamelGridFsObjectId gridfs.fileid -> CamelGridFsFileId The cascading rename of the auto-generated Endpoint DSL accessors on GridFsHeaderNameBuilder is included (gridfsOperation() -> gridFsOperation(), etc.) along with the regenerated component catalog. The upgrade-guide entry for this change is added on the main branch (per the backport upgrade-guide policy). Consistent with the same alignment applied to camel-lucene (CAMEL-23509), camel-jgroups (CAMEL-23510), camel-jgroups-raft (CAMEL-23511), and camel-cxf (CAMEL-23526). Reported by Claude Code on behalf of Andrea Cosentino. (cherry picked from commit 8f0b1ac) Signed-off-by: Andrea Cosentino <ancosen@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Aligns the values of the Exchange header constants in
GridFsConstants(camel-mongodb-gridfs) with the standardCamel<Component><Field>naming convention used across the rest of the component catalog. Brings the component in line with the parentcamel-mongodbcomponent, whereMongoDbConstants.OPERATION_HEADERis alreadyCamelMongoDbOperation.The Java field names are unchanged, so routes and code referencing the constants symbolically (e.g.
GridFsConstants.GRIDFS_OPERATION,GridFsConstants.GRIDFS_OBJECT_ID) continue to work without modification.Renames (string values only)
GRIDFS_OPERATIONgridfs.operationCamelGridFsOperationGRIDFS_METADATAgridfs.metadataCamelGridFsMetadataGRIDFS_CHUNKSIZEgridfs.chunksizeCamelGridFsChunkSizeGRIDFS_OBJECT_IDgridfs.objectidCamelGridFsObjectIdGRIDFS_FILE_ID_PRODUCEDgridfs.fileidCamelGridFsFileIdCascading regeneration
The Endpoint DSL header accessors on
GridFsHeaderNameBuildergot renamed accordingly (gridfsOperation()->gridFsOperation(), etc.). Both the constant-value rename and the DSL-accessor rename are documented incamel-4x-upgrade-guide-4_21.adoc.Context
Consistent with the same alignment recently applied to camel-lucene (CAMEL-23509), camel-jgroups (CAMEL-23510), camel-jgroups-raft (CAMEL-23511), and camel-cxf (CAMEL-23526). Affects 4.21.0 (this PR) and is queued for backport to 4.18.x / 4.14.x — the constants are identical on both maintenance branches.
Test plan
mvn -pl components/camel-mongodb-gridfs -am install— greenmvn clean install -DskipTestsfrom repo root — green; the catalog and Endpoint DSL regenerated artifacts are included in the commitGridFsConstants.GRIDFS_OPERATIONetc.), so no test-source changes are neededReported by Claude Code on behalf of Andrea Cosentino.