[Java] improve Flight DoPut busy wait
- Dominant language
- Java
- Stars
- 94
- Forks
- 152
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 11
Description
Currently the implementation of putNext in FlightClient.java busy-waits until gRPC indicates that the server can receive a message. We should either improve the busy-wait (e.g. add sleep times), or rethink the API and make it non-blocking.
**Reporter**: [David Li](https://issues.apache.org/jira/browse/ARROW-4484) / @lidavidm
**Note**: *This issue was originally created as [ARROW-4484](https://issues.apache.org/jira/browse/ARROW-4484). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
Contributor guide
Research direction
Read putNext in FlightClient.java and trace how it waits for gRPC to indicate that the server can receive a message. Resolve whether the scope is improving the busy-wait or changing the API to be non-blocking. Done means the chosen approach removes the reported busy-wait problem without leaving the API behavior undefined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, java
- Domain
- api, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100