Skip to content

CAMEL-23509: document 4.14.8 camel-lucene header rename in upgrade guide #23239

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
oscerd merged 1 commit into from
May 15, 2026
+17 −0
Merged

CAMEL-23509: document 4.14.8 camel-lucene header rename in upgrade guide #23239

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,6 +99,23 @@ Hazelcast topic, queue, map, list, set, or in one of the repositories
above must provide their own `Config` with a
`JavaSerializationFilterConfig` configured for their class names.

=== camel-lucene

The Exchange header values exposed by `LuceneConstants` have been renamed to follow the standard
Camel naming convention. The field names are unchanged, so routes referencing the constants
(`LuceneConstants.HEADER_QUERY`, `LuceneConstants.HEADER_RETURN_LUCENE_DOCS`) continue to work
without modification. However, routes that set or read these headers using the raw string values
must be updated:

* `QUERY` -> `CamelLuceneQuery`
* `RETURN_LUCENE_DOCS` -> `CamelLuceneReturnLuceneDocs`

As a consequence, the generated Endpoint DSL header accessors on `LuceneHeaderNameBuilder`
have been renamed accordingly:

* `qUERY()` -> `luceneQuery()`
* `returnLuceneDocs()` -> `luceneReturnLuceneDocs()`

== Upgrading from 4.14.2 to 4.14.3

=== camel-tika
Expand Down