[ https://issues.apache.org/jira/browse/IMPALA-6838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tianyi Wang updated IMPALA-6838: -------------------------------- Description: After IMPALA-5990, the catalog metadata sent through catalogd -> statestored -> imapald is compressed. But the responses of DDL operations, which goes directly from catalogd to impalad, is not compressed, and the data transmission between Java and C++ is still bounded by the 2GB limit. We should compress it as well to save network bandwidth and improve impala's capability to handle large metadata. (was: After IMPALA-5990, the catalog metadata sent through catalogd -> statestored -> imapald is compressed. But the responses of DDL operations, which goes directly from catalogd to impalad, is not compressed. We should compress it as well to save network bandwidth and improve impala's capability to handle large metadata.) > Compress metadata in DDL operations > ----------------------------------- > > Key: IMPALA-6838 > URL: https://issues.apache.org/jira/browse/IMPALA-6838 > Project: IMPALA > Issue Type: Improvement > Components: Catalog > Affects Versions: Impala 3.0, Impala 2.12.0 > Reporter: Tianyi Wang > Assignee: Tianyi Wang > Priority: Major > > After IMPALA-5990, the catalog metadata sent through catalogd -> statestored > -> imapald is compressed. But the responses of DDL operations, which goes > directly from catalogd to impalad, is not compressed, and the data > transmission between Java and C++ is still bounded by the 2GB limit. We > should compress it as well to save network bandwidth and improve impala's > capability to handle large metadata. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org