[Flight][Java] Add optional session headers
- Dominant language
- Java
- Stars
- 94
- Forks
- 152
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 11
Description
- Add a client middleware which receives and re-uses a session token from the server.
- Add a server middleware which, when encountering a request with no session header, creates a session on the backend, generates a token for it, and sends the token to the client in a header. The client can re-use this as indicated above.
- If the client has a session header, re-use the same session from the backend (report an error if an invalid session was used).
**Reporter**: [Tiffany Lam](https://issues.apache.org/jira/browse/ARROW-10427) / @tifflhl
**Note**: *This issue was originally created as [ARROW-10427](https://issues.apache.org/jira/browse/ARROW-10427). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
Contributor guide
Research direction
Start by locating the Java client and server middleware entry points responsible for request and response headers, then trace how backend sessions and invalid-session errors are represented. Define the client and server integration tests needed to cover token creation, reuse, and invalid tokens; done means both middleware paths consistently share the backend session.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100