oscerd opened a new pull request, #23232:
URL: https://github.com/apache/camel/pull/23232

   ## Backport of #23208 onto `camel-4.14.x`
   
   Cherry-pick of #23208 onto `camel-4.14.x` for the 4.14.8 release line.
   
   **Original PR:** #23208 — CAMEL-23509: camel-lucene - align Exchange header 
constant values with Camel naming convention
   **Target branch:** `camel-4.14.x`
   **Conflicts resolved:** the `camel-4x-upgrade-guide-4_21.adoc` hunk from the 
source PR was dropped (file does not exist on this branch). A matching entry 
will be added to `camel-4x-upgrade-guide-4_14.adoc` on `main` via 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 
`LuceneConstants` to follow the standard `CamelLucene*` Camel naming convention:
   
   * `LuceneConstants.HEADER_QUERY`: `QUERY` -> `CamelLuceneQuery`
   * `LuceneConstants.HEADER_RETURN_LUCENE_DOCS`: `RETURN_LUCENE_DOCS` -> 
`CamelLuceneReturnLuceneDocs`
   
   The 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 `LuceneHeaderNameBuilder` are also renamed:
   
   * `qUERY()` -> `luceneQuery()`
   * `returnLuceneDocs()` -> `luceneReturnLuceneDocs()`
   
   JIRA: https://issues.apache.org/jira/browse/CAMEL-23509
   
   _Claude Code on behalf of Andrea Cosentino_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to