You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Zhihua Deng (Jira)" <ji...@apache.org> on 2025/03/17 09:05:00 UTC

[jira] [Updated] (HIVE-28824) Metastore should also respect the max message size the client can send

     [ https://issues.apache.org/jira/browse/HIVE-28824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhihua Deng updated HIVE-28824:
-------------------------------
    Description: 
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. 

  was:
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 sends 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. 


> Metastore should also respect the max message size the client can send
> ----------------------------------------------------------------------
>
>                 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
>
> 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)