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
We have a use case in our production environment where getFlightInfo can take longer than a second and having a blocking getFlightInfo is a problem. Since many other methods in FlightProducer is non blocking we should also have a non blocking getFlightInfo
The code would look something like this with minimum impact to all the implementations
/**
* Get information about a particular data stream.
*
* @param context Per-call context.
* @param descriptor The descriptor identifying the data stream.
* @return Metadata about the stream.
*/
FlightInfo getFlightInfo(CallContext context, FlightDescriptor descriptor);
/**
* Get information about a particular data stream.
*
* @param context Per-call context.
* @param descriptor The descriptor identifying the data stream.
* @param listener An interface for sending data back to the client.
*/
default void getFlightInfo(CallContext context, FlightDescriptor descriptor, StreamListener<FlightInfo> listener ){
FlightInfo flightInfo = getFlightInfo(context, descriptor);
listener.onNext(flightInfo);
listener.onCompleted();
}
/**
*
* @return true if blocking (default) version of getFlightInfo needs to be used by FlightService.
*/
default boolean isBlockingFlightInfo() {
return true;
}
I'd suggest using gRPC directly (FlightGrpcUtils) to gain access to advanced APIs; I think trying to do more and more wrapping of the gRPC API surface is going to prove ineffective, especially given limited maintainer bandwidth. If there any ways we can make this easier I'd be all ears
I did look at those classes including FlightService as well as FlightBindingService but could not come up with approach without doing to much refactoring to my code base. We have made significant investment in FlightSqlProducer and trying to come up with a solution which would required least bit of refactoring
Let me look more, I will update the bug later
Activity
lidavidm commentedon Apr 20, 2025
I'd suggest using gRPC directly (FlightGrpcUtils) to gain access to advanced APIs; I think trying to do more and more wrapping of the gRPC API surface is going to prove ineffective, especially given limited maintainer bandwidth. If there any ways we can make this easier I'd be all ears
tanejagagan commentedon Apr 21, 2025
I did look at those classes including FlightService as well as FlightBindingService but could not come up with approach without doing to much refactoring to my code base. We have made significant investment in FlightSqlProducer and trying to come up with a solution which would required least bit of refactoring
Let me look more, I will update the bug later
MINOR: Bump org.apache.commons:commons-text from 1.13.1 to 1.15.0 (#956)