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

Alexander Behm resolved IMPALA-5881.
------------------------------------
    Resolution: Won't Fix

We decided to fix this in a different way. See IMPALA-5990

> Use native allocations to workaround JVM limitations in getAllCatalogObjects()
> ------------------------------------------------------------------------------
>
>                 Key: IMPALA-5881
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5881
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Catalog
>            Reporter: bharath v
>            Assignee: bharath v
>
> When {{compact_catalog_topic=true}}, we need to compact the output of 
> getAllCatalogObjects() since it can potentially be quite big (on large 
> clusters) and we have the risk of running into JVM array limitations if we 
> use the regular TBinaryProtocol.Currently we only compact the output between 
> backend < - > statestore, but it makes sense to do it between backend< - 
> >frontend in the JNI too.
> Additionally, figure out ways to use native allocations to workaround JVM 
> array size limitations during thrift serialization.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to