From de9de5c8e5f4fc1dd7e5316d21e3d46b2a641379 Mon Sep 17 00:00:00 2001 From: Andrea Cosentino Date: Thu, 14 May 2026 19:47:15 +0200 Subject: [PATCH] CAMEL-23509: document 4.14.8 camel-lucene header rename in upgrade guide Signed-off-by: Andrea Cosentino --- .../ROOT/pages/camel-4x-upgrade-guide-4_14.adoc | 17 +++++++++++++++++ 1 file changed, 17 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 dfab1bd1be375..f0823cae1f05e 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 @@ -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