[backport camel-4.18.x] CAMEL-23509: camel-lucene - align Exchange header constant values with Camel naming convention#23220
Merged
oscerd merged 1 commit intoMay 14, 2026
Conversation
…h Camel naming convention Signed-off-by: Andrea Cosentino <ancosen@gmail.com>
davsclaus
approved these changes
May 14, 2026
oscerd
added a commit
that referenced
this pull request
May 14, 2026
Doc-sync companion to backport #23220 (camel-lucene header rename onto camel-4.18.x). Per the project's backport upgrade-guide policy, the camel-4x-upgrade-guide-4_XX.adoc files live only on main and act as the canonical history across all releases. This PR adds the camel-lucene entry to camel-4x-upgrade-guide-4_18.adoc under the "Upgrading from 4.18.1 to 4.18.3" section, documenting the rename of the LuceneConstants Exchange header string values to the CamelLucene* convention. Closes #23222
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.
Backport of #23208 onto
camel-4.18.xCherry-pick of #23208 onto
camel-4.18.xfor the 4.18.3 release line.Original PR: #23208 — CAMEL-23509: camel-lucene - align Exchange header constant values with Camel naming convention
Target branch:
camel-4.18.xConflicts resolved: the
camel-4x-upgrade-guide-4_21.adochunk from the source PR was dropped (file does not exist on this branch). A matching entry will be added tocamel-4x-upgrade-guide-4_18.adoconmainvia a follow-up PR, in line with the project's backport upgrade-guide policy.Original description
Renames the values of the Exchange header constants exposed by
LuceneConstantsto follow the standardCamelLucene*Camel naming convention:LuceneConstants.HEADER_QUERY:QUERY->CamelLuceneQueryLuceneConstants.HEADER_RETURN_LUCENE_DOCS:RETURN_LUCENE_DOCS->CamelLuceneReturnLuceneDocsThe field names are unchanged, so routes that reference the constants continue to work without modification. Routes that set or read these headers using the raw string values must be updated.
As a consequence of the value rename, the auto-generated Endpoint DSL header accessors on
LuceneHeaderNameBuilderare also renamed:qUERY()->luceneQuery()returnLuceneDocs()->luceneReturnLuceneDocs()JIRA: https://issues.apache.org/jira/browse/CAMEL-23509
Claude Code on behalf of Andrea Cosentino