IMPALA-10179: After join inversion inherit the left child's parallelism

The planner makes a cost based decision to invert a join - i.e swap
left and right child - based on cardinality, row size and parallelism
of both sides. The join node's numNodes and numInstances attributes were
originally set based on the left child's values. These were not getting
reset after the inversion and the plan shows the original value,
although the backend actually uses the correct value from the left
input..so this mainly affects planner estimates.

This patch fixes this behavior by inheriting the new left child's
parallelism (numNodes and numInstances) after inversion. A common case
where the join inputs get flipped is when the original query has a
left semi join (IN, EXISTS etc.) and the subquery has a large
cardinality compared to the outer query. This gets converted to a
right semi join.  This pattern occurs for example in TPC-DS q10, q35,
q69.

Testing:
 - Updated the plans for several TPC-DS queries to reflect the modified
   parallelism.  11 queries had the join fragment 'instances' increase
   from either 1 or 2 to 6 (for planner tests hosts = 3 and mt_dop = 2).

   There were also 4 queries where the parallelism reduced. Based on an
   initial check, these changes seem expected.

   TODO: Check if this reduction is expected based on the costing. One
   option may be to use a max(left parallelism, right parallelism) value
   to avoid unintended side effects.

 - Couple of TPC-H queries also had increase in parallelism.
 - Ran e2e TPC-DS queries.
 - TODO: test performance on larger scale factor

Change-Id: I01ba559034ad76f7ccee41f237c81b29d8402950
Reviewed-on: http://gerrit.cloudera.org:8080/16480
Reviewed-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
78 files changed
tree: 46b508fcb6e67bf91d2b9638017710c0039af90d
  1. be/
  2. bin/
  3. cmake_modules/
  4. common/
  5. docker/
  6. docs/
  7. ext-data-source/
  8. fe/
  9. impala-parent/
  10. infra/
  11. lib/
  12. query-event-hook-api/
  13. security/
  14. shaded-deps/
  15. shell/
  16. ssh_keys/
  17. testdata/
  18. tests/
  19. www/
  20. .clang-format
  21. .clang-tidy
  22. .gitattributes
  23. .gitignore
  24. buildall.sh
  25. CMakeLists.txt
  26. EXPORT_CONTROL.md
  27. LICENSE.txt
  28. LOGS.md
  29. NOTICE.txt
  30. README-build.md
  31. README.md
  32. setup.cfg
README.md

Welcome to Impala

Lightning-fast, distributed SQL queries for petabytes of data stored in Apache Hadoop clusters.

Impala is a modern, massively-distributed, massively-parallel, C++ query engine that lets you analyze, transform and combine data from a variety of data sources:

  • Best of breed performance and scalability.
  • Support for data stored in HDFS, Apache HBase, Apache Kudu, Amazon S3, Azure Data Lake Storage, Apache Hadoop Ozone and more!
  • Wide analytic SQL support, including window functions and subqueries.
  • On-the-fly code generation using LLVM to generate lightning-fast code tailored specifically to each individual query.
  • Support for the most commonly-used Hadoop file formats, including Apache Parquet and Apache ORC.
  • Support for industry-standard security protocols, including Kerberos, LDAP and TLS.
  • Apache-licensed, 100% open source.

More about Impala

To learn more about Impala as a business user, or to try Impala live or in a VM, please visit the Impala homepage. Detailed documentation for administrators and users is available at Apache Impala documentation.

If you are interested in contributing to Impala as a developer, or learning more about Impala's internals and architecture, visit the Impala wiki.

Supported Platforms

Impala only supports Linux at the moment. Impala supports x86_64 and has experimental support for arm64 (as of Impala 4.0). Impala Requirements contains more detailed information on the minimum CPU requirements.

Export Control Notice

This distribution uses cryptographic software and may be subject to export controls. Please refer to EXPORT_CONTROL.md for more information.

Build Instructions

See Impala's developer documentation to get started.

Detailed build notes has some detailed information on the project layout and build.