[IMPALA-7536] Re-evaluate Avro/Kudu/HBase table performance with fetch-from-catalogd

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Catalog
• Labels: catalog-v2
• Epic Color: ghx-label-6
• Assignee: Unassigned
• Reporter: Todd Lipcon
• Created: 05/Sep/18 20:14
• Updated: 21/Dec/20 19:33

Description

The Avro, Kudu,and HBase table support for LocalCatalog was written with "fetch-from-source" in mind. Thus, they spend considerable effort to determine the schema on the impalad side when the table is loaded. In "fetch from catalogd" mode, the catalogd has already done this schema resolution, and we're likely better off not doing the extra work on the impalad. We should do a pass back over those table types to make sure there isn't unnecessary work being performed.