[SPARK-49489][SQL][HIVE] HMS client respects hive.thrift.client.maxmessage.size
#50022
+80
−12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Port HIVE-26633 for Spark HMS client.
Why are the changes needed?
See discussion in #46468 (comment)
Does this PR introduce any user-facing change?
No, it fixes the bug introduced by an unreleased change, namely SPARK-47018.
How was this patch tested?
This must be tested manually, as the current Spark UT does not cover the remote HMS cases.
I constructed a test case in a testing Hadoop cluster with a remote HMS.
Firstly, create a table with a large number of partitions.
Then try to tune
hive.thrift.client.max.message.size
and run a query that would triggergetPartitions
thrift call. For example, when set to 1mb, it throwsTTransportException: MaxMessageSize reached
, and the exception disappers after boosting the value.Was this patch authored or co-authored using generative AI tooling?
No.