-
Notifications
You must be signed in to change notification settings - Fork 935
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
[Bug] MaxMessageSize Reached When Querying ICEBERG Table with Kyuubi 1.9 #6594
Labels
Comments
Hello @zhanghe-git, |
This is caused by Thrift upgrading, from 0.9.3-1 to 0.16.0.
We should make the thrift client's max message size configurable |
4 tasks
pan3793
added a commit
that referenced
this issue
Aug 27, 2024
…figurable Fix #6594. This PR ports HIVE-26633(apache/hive#3674): Make thrift client maxMessageSize configurable to fix a regression after upgrading Thrift 0.16 in 1.9.0. - [x] Bugfix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) --- - [x] This patch was not authored or co-authored using [Generative Tooling](https://www.apache.org/legal/generative-tooling.html) **Be nice. Be informative.** Closes #6631 from pan3793/thrift-max-size. Closes #6594 e4841c8 [Cheng Pan] [KYUUBI #6594] Port HIVE-26633: Make thrift client maxMessageSize configurable Authored-by: Cheng Pan <[email protected]> Signed-off-by: Cheng Pan <[email protected]> (cherry picked from commit 11de72f) Signed-off-by: Cheng Pan <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Code of Conduct
Search before asking
Describe the bug
I encountered an issue when querying an ICEBERG table using a self-built Kyuubi (version 1.9.1) with Spark.
The query involves retrieving a single row of data that is 100MB in size.
While the query executes successfully on the Spark side, the Kyuubi side reports a MaxMessageSize reached error.
I attempted to resolve this by adjusting the kyuubi.frontend.thrift.max.message.size parameter, but the error persists.
It seems that some max size limit is being reached in Kyuubi. How can this be adjusted?
Additional information: When using Alibaba Cloud's EMR with its built-in Kyuubi (version 1.7.1), the query returns successfully. (My kyuubi-defaults configuration is consistent with Alibaba Cloud's setup.)
Affects Version(s)
1.9.1
Kyuubi Server Log Output
Kyuubi Engine Log Output
No response
Kyuubi Server Configurations
No response
Kyuubi Engine Configurations
No response
Additional context
No response
Are you willing to submit PR?
The text was updated successfully, but these errors were encountered: