-
Notifications
You must be signed in to change notification settings - Fork 842
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default FlightSqlService Implementations #4372
Comments
I think the trait in question is https://docs.rs/arrow-flight/41.0.0/arrow_flight/sql/server/trait.FlightSqlService.html (and it has 40 methods!) |
SGTM. Another potential cleanup avenue would be exposing higher level abstractions (i.e. the ability to provide an object representing over database structure), then the 20 of these are |
The trait currently does not have many default implementations, but it does have a lot of methods. This PR adds default implementations for all methods returning Status::unimplemented to fix apache#4372
The trait currently does not have many default implementations, but it does have a lot of methods. This PR adds default implementations for all methods returning Status::unimplemented to fix apache#4372
The trait currently does not have many default implementations, but it does have a lot of methods. This PR adds default implementations for all methods returning Status::unimplemented to fix apache#4372
The trait currently does not have many default implementations, but it does have a lot of methods. This PR adds default implementations for all methods returning Status::unimplemented to fix #4372
|
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Noticed whilst working on apache/datafusion#6374, this trait is now substantial and requires a significant amount of boilerplate to implement a service, that may not be interested in a significant portion of the API surface
Describe the solution you'd like
I would like default implementations that return
Status::unimplemented
for all the trait methodsDescribe alternatives you've considered
We could only provide impls for some subset, but this is likely more confusing than just providing blanket implementations for all of them
Additional context
FYI @alamb @avantgardnerio
The text was updated successfully, but these errors were encountered: