COM_CHANGE_USER may need session migration
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 73
- Forks
- 41
- Avg merge
- 21h 3m
- Merged PRs (30d)
- 21
Description
Development Task
Currently, TiProxy routes connections based on the username. If a session has sent COM_CHANGE_USER, the username may change and it may need to connect to another TiDB instance.
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
No files or tests are named. Start by tracing COM_CHANGE_USER handling and the username-based connection-routing path; determine when a session must migrate to another TiDB instance. Done means the required migration behavior is defined and covered by validation for sessions whose username changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100