ydb-platform / ydb-platform/ydb-java-sdk
Add control of session state
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 53
- Forks
- 40
- Avg merge
- 9h 51m
- Merged PRs (30d)
- 7
Description
Current implementation of sessions and the session pool doesn't include the control of the session state.
And we often have next problems:
- Usage of session after closing
- Parallel usage of one session
- Deleting session by client error or canceling
We can resolve these problem by adding the control of current session state - idle, active, executing, canceled and etc. And every action on the session can check this state and returns an error if client uses session in wrong way
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 locating the session and session pool implementations, then determine how session lifecycle actions are currently handled. Done should include defined states and validation that rejects use after closing, parallel use, and deletion after client errors or cancellation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100