Croway opened a new pull request, #27814: URL: https://github.com/apache/camel/pull/27814
Fixes https://issues.apache.org/jira/browse/CAMEL-25536 `camel_migration_guide_search` returned whole release sections of the upgrade guides, ranked by how many query words they contained anywhere, with the first 30 lines as the snippet. A Camel 2 to 4 question was answered from the 4.21 or 4.14 notes with a snippet about an unrelated component; in an evaluation of coding agents none of 13 calls returned a relevant section. - The guides are indexed at the `===` topic level (1,372 entries instead of 158), each titled with its release heading as context, e.g. "Upgrading Camel 4.20 to 4.21 / camel-cxf". - BM25 scoring with length normalisation, a bonus for a term in the topic heading, stop words (camel, migration, upgrade, version, guide, ...) dropped, the existing typo tolerance kept at reduced weight. - Optional `fromVersion` / `toVersion`: only the guides between the two versions are searched, and the major migration guides (2.x to 3.0, 3.x to 4.0) come first when the range crosses them. - The snippet is the lines around the best match, not the start of the section. - A minimum score and term coverage: an unrelated query returns no results and a hint to rephrase or ask `camel_catalog_doc`, instead of unrelated sections. The three queries of the issue now put the camel-cxf entry, the camel-mail breaking-change entry and the 2.x to 3.0 "Migrating Camel applications" entry first. Tests: `Migration*Test` in camel-jbang-mcp (22 tests), the full module suite passes. _Claude Code on behalf of Croway_ -- 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]
