[
https://issues.apache.org/jira/browse/HIVE-28824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhihua Deng resolved HIVE-28824.
--------------------------------
Fix Version/s: 4.1.0
Resolution: Fixed
Fix has been pushed to master. Thank you [~dkuzmenko] for the review!
> Metastore should also respect the max thrift message size
> ---------------------------------------------------------
>
> Key: HIVE-28824
> URL: https://issues.apache.org/jira/browse/HIVE-28824
> Project: Hive
> Issue Type: Bug
> Reporter: Zhihua Deng
> Assignee: Zhihua Deng
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.1.0
>
>
> Per HIVE-26633, we can configure the Thrift MaxMessageSize via
> hive.thrift.client.max.message.size, but it only takes effect on the client
> side, the server still follows the default 100M. If the message the client
> sent is greater than 100M, Metastore will get the
> TTransportException(END_OF_FILE), then close the connection silently. On the
> client side, it can see the odd exception indicating the connection is
> closed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
