spring-projects / spring-projects/spring-ai
CompressionQueryTransformer sometimes fails to correctly transform user issues
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.5k
- Forks
- 2.9k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 6
Description
When using CompressionQueryTransformer, sometimes there may be a situation where the result of this transformation is the transformation result of the previous problem, and CompressionQueryTransformer does not properly transform the current user problem. This problem often occurs, and I'm not sure if it's a problem with my usage. Has anyone encountered it before?
My code is as follows:
This is my historical Q&A data, and the red box shows that the rewritten question is the previous rewritten question:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with CompressionQueryTransformer and reproduce the behavior using the usage example and historical Q&A data shown in the issue. Trace how the current user problem and previous rewritten question are handled, then verify that each input produces its own transformation result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- ai
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100