| commit | 54642b2549c38625c868f09815b61170e568cdb9 | [log] [tgz] |
|---|---|---|
| author | Michael Smith <michael.smith@cloudera.com> | Wed Mar 06 14:00:18 2024 -0800 |
| committer | Impala Public Jenkins <impala-public-jenkins@cloudera.com> | Fri Mar 08 00:36:04 2024 +0000 |
| tree | ea385bb11395e766cb1d21f6d399103080fb449c | |
| parent | befa93ffa6b0fa50c614b6e24faf25443ec50d90 [diff] |
IMPALA-12878: Report invalid query if finalized Fixes a case introduced by IMPALA-12493 where a query is closed again in the middle of unregistering - which appears to be possible with cancel_query_and_validate_state - returns "Query not yet running" instead of "Invalid or unknown query handle". IMPALA-12493 moved checks for whether a query is inflight before an atomic CompareAndSwap to mark a QueryDriver as finalized. As part of that change, a query that was Finalized and removed from inflight_queries - but not yet removed from query_driver_map_ - could report "Query not yet running". Updates the check for that error to also verify the query has not been finalized; if it has, we let the next conditional handle that case and return "Invalid or unknown query handle". Also ensures cancelled queries are closed in test_web_pages tests so assertions that num_in_flight_queries == 0 at the start of tests are valid when running the whole suite serially. This doesn't come up in automated tests because the cases that care about that assertion are marked execute_serially, while the cases that failed to close a query were not. Testing: adds a test to test_cancellation that ensures we get the expected "Invalid or unknown query handle" when close() is delayed in calling QueryDriver::Finalize. Change-Id: I3bf910f499147a09352f9dcb755037b0d8616dfd Reviewed-on: http://gerrit.cloudera.org:8080/21110 Reviewed-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com> Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
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:
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.
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.
Impala runs on Linux systems only. The supported distros are
Other systems, e.g. SLES12, may also be supported but are not tested by the community.
This distribution uses cryptographic software and may be subject to export controls. Please refer to EXPORT_CONTROL.md for more information.
See Impala's developer documentation to get started.
Detailed build notes has some detailed information on the project layout and build.