-
Notifications
You must be signed in to change notification settings - Fork 11
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
[ADBC][FlightSQL][Java] 'Encountered end-of-stream mid-frame' upgrading from Arrow 17 -> 18 #42
Comments
I missed this, sorry. This is only happening via ADBC, you say, not via the regular FlightSqlClient? |
Also, what version of grpc-netty do you end up pulling in? grpc/grpc-java#11284 |
aha, 1.60.0 atm. will see what's pulling that in |
upgrading to 18.1.0, ADBC 0.15.0 (and hence grpc-netty 1.65.0) gives me a different error, at least 😅 Through FlightSqlClient:
Currently wondering whether this is the 0.14.0 -> 0.15.0 upgrade, if there was a breaking change there... 👀 I'll close this one for now and keep digging, given I'm not seeing the original error - but if you happen to know off-hand what might be causing this other one I'm all ears 😆 |
Sorted - needed to migrate |
Ah! Thanks for reporting back |
Describe the bug, including details regarding any error messages, version, and platform.
Hey folks - I seem to have a regression upgrading to Arrow 18 in an E2E ADBC (via FlightSQL) test:
(unfortunately this is the only stack trace I'm getting atm)
Our implementation of the FlightSQL server is pretty bare-bones right now so entirely possible it's something we're doing wrong - raising here just in case anyone else is running into it (feel free to close if not!)
Cheers,
James
(our issue: xtdb/xtdb#3833)
Component(s)
FlightRPC, Java, Other
The text was updated successfully, but these errors were encountered: