[GraalVM] Include missing grpc configurations for Direct Path support #3239
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Comments
mpeddada1
added
type: feature request
|
The failures we ran into all appears to be for protobuf generated classes (messages, builders, enums). Rather than grpc classes themselves. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This was discovered during an offline discussion with @BenWhitehead on googleapis/java-storage#2716 where Storage ran into a run-time failures in graalvm when adding Direct Path support.
The solution (in progress) has been to include reflection configurations for
io.grpcclasses (googleapis/java-storage#2716).In the future, we should consider hosting or generating these generic configurations in
sdk-platform-javato avoid duplicating this effort for libraries considering adding direct path support in the future.cc/ @burkedavison
The text was updated successfully, but these errors were encountered: