[Flight] Make it possible to use native gRPC Java APIs, and/or simplify the implementation

Open
#568 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
grpc, java
Domain
api, backend-api-design

Research direction

Start by reviewing the grpc-java PR 10318 and the Flight DoGet, DoPut, and DoExchange interfaces described in the issue. Compare using the native blocking streaming APIs with the current wrappers, including the server-side implications. Done should mean a clearly chosen approach that either enables direct gRPC API use or demonstrably simplifies the implementation.

Written by the indexing model from the issue text.

Description

Type: enhancement
Describe the enhancement requested

https://github.com/grpc/grpc-java/pull/10318 introduces a new type of blocking stub in grpc-java which handles streaming calls. This could drastically simplify DoGet/DoPut/DoExchange which try to present blocking interfaces to nonblocking APIs. However, preferably we would make it possible to use gRPC APIs directly instead of making users wait for us to wrap new APIs in even less documented new APIs. Also, it's not clear that this simplifies the server side at all (unfortunately).

Dominant language
Java
Stars
95
Forks
154
Avg merge
2d 10h
Merged PRs (30d)
11

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/arrow-java

All issues in apache/arrow-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.