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

   ## Summary
   
   Backport to `camel-4.18.x` of the `camel-solr` Exchange header prefix 
alignment merged to `main` in #23410.
   
   Renames the two prefix constants in `SolrConstants`:
   
   - `SolrConstants.HEADER_FIELD_PREFIX` value: `"SolrField."` -> 
`"CamelSolrField."`
   - `SolrConstants.HEADER_PARAM_PREFIX` value: `"SolrParam."` -> 
`"CamelSolrParam."`
   
   The Java field names are unchanged, so routes referencing the constants 
symbolically are unaffected. Routes that set the headers by their literal 
string value must adopt the new prefix — documented in the 4.18 upgrade-guide 
entry added by this PR.
   
   Completes the `CamelSolrXxx` alignment started in CAMEL-21697 (which renamed 
the other `SolrConstants` Exchange header constants but missed the two prefix 
constants). Consistent with the alignment applied to sibling components in 
CAMEL-23506, CAMEL-23522, CAMEL-23526 and CAMEL-23532.
   
   ## What changed
   
   - `SolrConstants.java`: prefix values renamed.
   - `SolrProducer.java` / `SolrRequestConverter.java`: inline javadoc comments 
updated.
   - `SolrInsertAndDeleteTest`, `SolrPingAndSearchTest`, `SolrTestSupport`: 
integration-test header literals updated.
   - `solr-component.adoc`: documentation snippets updated.
   - `camel-4x-upgrade-guide-4_18.adoc`: new `=== camel-solr` entry under the 
4.18.2 -> 4.18.3 section.
   
   > Note: the canonical `camel-4x-upgrade-guide-4_18.adoc` on `main` will be 
updated with the same entry in a follow-up doc-sync PR, per the backport 
upgrade-guide policy.
   
   ## Test plan
   
   - [x] `mvn -DskipTests formatter:format impsort:sort install` in 
`components/camel-solr` — BUILD SUCCESS.
   - [x] Cherry-pick of the `main` squash commit (`4578a9014a6`); the 
upgrade-guide note was redirected from the `4_21` guide to the `4_18` guide for 
this release line.
   - [ ] CI green.
   
   ---
   
   _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