JiriOndrusek opened a new pull request, #9145:
URL: https://github.com/apache/camel-quarkus/pull/9145
Fixes #9144.
Renames the segment metadata keys from `camel_quarkus_*` to
`camel_ingest_pipeline` / `camel_ingest_document_id` — the names used by the
`camel-langchain4j-ingest` component (Camel 4.23, CAMEL-24621) that the
extension will delegate to (#9142).
Doing the rename in 3.40.0 makes LTS stores compatible with the delegated
engine up front, so LTS users never re-ingest. Only 3.39.x stores are affected;
the migration guide covers the remedies. No config, API or behaviour change
otherwise.
Verified: 23 deployment suites, 12 JVM + 12 native ITs green.
_Claude Code on behalf of @JiriOndrusek_
<!-- Uncomment and fill this section if your PR is not trivial
[ ] An issue should be filed for the change unless this is a trivial change
(fixing a typo or similar). One issue should ideally be fixed by not more than
one commit and the other way round, each commit should fix just one issue,
without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful and properly
spelled subject line and body. Copying the title of the associated issue is
typically enough. Please include the issue number in the commit message
prefixed by #.
[ ] The pull request description should explain what the pull request does,
how, and why. If the info is available in the associated issue or some other
external document, a link is enough.
[ ] Phrases like Fix #<issueNumber> or Fixes #<issueNumber> will auto-close
the named issue upon merging the pull request. Using them is typically a good
idea.
[ ] Please run mvn process-resources -Pformat (and amend the changes if
necessary) before sending the pull request.
[ ] Contributor guide is your good friend:
https://camel.apache.org/camel-quarkus/latest/contributor-guide.html
-->
--
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]
