https://community.cloudera.com/t5/Support-Questions/Impala-3-2-0-performance-degradation-while-querying-views/m-p/301654#M220791 <P>I'm not aware of any significant regressions in planning time between those versions. There were actually some major improvements for some common types of complex queries with many columns -&nbsp;<A href="https://issues.apache.org/jira/browse/IMPALA-4242" target="_blank" rel="noopener">https://issues.apache.org/jira/browse/IMPALA-4242</A></P><P>&nbsp;</P><P>So there's no known issue that this obviously maps to (the problem described is quite abstract so take that with a grain of salt). There were a couple of issues related to authorization and Sentry that I initially thought about but I believe had been addressed&nbsp;by 6.3.1 (keep in mind that there are quite a lot of improvements in CDH6.3.1 relative to Impala 3.2.0). Anyway I don't want to speculate too much without even knowing which part of planning may be slow.</P><P>&nbsp;</P><P>Can you provide query profiles for those queries? Or if that isn't possible, at least the "Query Timeline" and "Planner Timeline" for the fast and slow queries.</P><P>&nbsp;</P><P>Edit: just to be clear, the info you provided about the views was useful, but this seems like it's probably something pretty specific to your queries so it's likely any investigation is going to be most fruitful starting from data about the specific queries in your environment.</P> Wed, 19 Aug 2020 17:25:22 GMT Tim Armstrong 2020-08-19T17:25:22Z