docs(retrieval): note intent-analysis model is configurable via query_planner (#2224)#2269
Merged
qin-ctx merged 2 commits intoMay 28, 2026
Merged
Conversation
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
PR Code Suggestions ✨No code suggestions found for the PR. |
qin-ctx
approved these changes
May 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The retrieval concept doc (
docs/{en,zh}/concepts/07-retrieval.md) describes the Intent Analysis stage as "IntentAnalyzer uses LLM to analyze query intent", but #2224 (feat(search) Add lightweight query planner config for intent analysis) made the model for this exact stage separately configurable via the newquery_plannerconfig (rewiringintent_analyzer.pyto callconfig.get_query_planner(), which falls back tovlm).#2224 self-documented the knob in
guides/01-configuration.md(### query_planner), but the concept doc that explains the intent-analysis mechanism still implies a single fixed LLM. Users reading this doc to understand/tune the stage won't discover they can point it at a cheaper dedicated model.This adds a one-sentence note + cross-link to the configuration guide, in both EN and ZH (byte-structurally mirrored concept docs). Pure docs, no behavior change.