You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While implementing #5339, I wished I could have used the Flight POJOs (org.apache.arrow.flight) everywhere instead of the Flight protobufs (org.apache.arrow.flight.impl); while it would be a breaking change, it would be relatively straightforward to update all of our code save for the grpc sending layer, to work directly with Flight POJOs.
For example, io.deephaven.server.session.ActionResolver was implemented with org.apache.arrow.flight.Action, org.apache.arrow.flight.ActionType, and org.apache.arrow.flight.Result as opposed to org.apache.arrow.flight.impl.Flight.Action, org.apache.arrow.flight.impl.Flight.ActionType, and org.apache.arrow.flight.impl.Flight.Result.
The text was updated successfully, but these errors were encountered:
While implementing #5339, I wished I could have used the Flight POJOs (
org.apache.arrow.flight
) everywhere instead of the Flight protobufs (org.apache.arrow.flight.impl
); while it would be a breaking change, it would be relatively straightforward to update all of our code save for the grpc sending layer, to work directly with Flight POJOs.For example,
io.deephaven.server.session.ActionResolver
was implemented withorg.apache.arrow.flight.Action
,org.apache.arrow.flight.ActionType
, andorg.apache.arrow.flight.Result
as opposed toorg.apache.arrow.flight.impl.Flight.Action
,org.apache.arrow.flight.impl.Flight.ActionType
, andorg.apache.arrow.flight.impl.Flight.Result
.The text was updated successfully, but these errors were encountered: