IMPALA-14985: Cleanup tests with unused 'vector' in EE tests

Having 'vector' argument leads to running a test as parametrized,
so running it with multiple parameter vectors. These parameters
don't affect how queries run unless passed to functions like
run_test_case() explicitly.

Note that unused 'vector's can give the false impression of
affecting the query options of queries run by default clients
as query option CLIENT_IDENTIFIER is actually modifed based
on the parameter vector using pytest hook pytest_runtest_logstart
and connections' clear_configuration and create_connection functions.

One example (TestIOMetrics) was found where the intention was to
pass num_nodes=1 but this didn't happen.

A test bug found during this change is that there were test classes
where "skip if not exhaustive" logic was implemented within
add_test_dimensions(), but this didn't affect non-parametrized
tests that were still run in core builds. This is fixed by
checking exploration strategy elsewhere.

The change also cleans up add_test_dimensions() functions which
are not used as the test class has no test function with
'vector' parameter.

Testing:
- passed exhaustive tests

Generated by: copilot + Claude Sonnet 4.6

Change-Id: I8e2a8fe333e33a906178a0821eb554890be26132
Reviewed-on: http://gerrit.cloudera.org:8080/24296
Reviewed-by: Noemi Pap-Takacs <npaptakacs@cloudera.com>
Tested-by: Csaba Ringhofer <csringhofer@cloudera.com>
54 files changed
tree: 4a5f444e8a38cd820200956c40d3f2af3e43a9b7
  1. .devcontainer/
  2. be/
  3. bin/
  4. cmake_modules/
  5. common/
  6. docker/
  7. docs/
  8. fe/
  9. infra/
  10. java/
  11. lib/
  12. package/
  13. security/
  14. shell/
  15. ssh_keys/
  16. testdata/
  17. tests/
  18. www/
  19. .asf.yaml
  20. .clang-format
  21. .clang-tidy
  22. .gitattributes
  23. .gitignore
  24. .isort.cfg
  25. buildall.sh
  26. CMakeLists.txt
  27. EXPORT_CONTROL.md
  28. LICENSE.txt
  29. LOGS.md
  30. NOTICE.txt
  31. README-build.md
  32. README.md
  33. setup.cfg
README.md

Welcome to Impala

Lightning-fast, distributed SQL queries for petabytes of data stored in open data and table formats.

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:

More about Impala

The fastest way to try out Impala is a quickstart Docker container. You can try out running queries and processing data sets in Impala on a single machine without installing dependencies. It can automatically load test data sets into Apache Kudu and Apache Parquet formats and you can start playing around with Apache Impala SQL within minutes.

To learn more about Impala as a user or administrator, or to try Impala, 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.

Supported OS Distributions

Impala runs on Linux systems only. The supported distros are

  • Ubuntu 16.04/18.04
  • CentOS/RHEL 7/8

Other systems, e.g. SLES12, may also be supported but are not tested by the community.

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.