JiriOndrusek opened a new pull request, #9163: URL: https://github.com/apache/camel-quarkus/pull/9163
fixes https://github.com/apache/camel-quarkus/issues/9162 follows https://github.com/apache/camel-quarkus/pull/9145 The default id header of consumer-fed pipelines is changed in Camel 4.23.0 (to `CamelLangChain4jIngestDocumentId`). The 3.39 name CamelIngestDocumentId is still read as a deprecated fallback when the new header is absent - the new one wins when both are set - and IngestHeaders keeps it as LEGACY_DOCUMENT_ID. Documented in the migration guide. Verified: 23 deployment test suites, 13 JVM integration tests green. <!-- 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]
