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

Posted to issues-all@impala.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2018/09/05 20:15:00 UTC

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

Todd Lipcon created IMPALA-7536:
-----------------------------------

             Summary: Re-evaluate Avro/Kudu/HBase table performance with fetch-from-catalogd
                 Key: IMPALA-7536
                 URL: https://issues.apache.org/jira/browse/IMPALA-7536
             Project: IMPALA
          Issue Type: Sub-task
            Reporter: Todd Lipcon


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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org