a68f716458
When EventProcessor is paused, e.g. due to a global INVALIDATE METADATA operation, in alterTableOrViewRename() we don't fetch the event id of the ALTER_TABLE event. This causes the createEventId of the new table being -1 and the DeleteEventLog entry of the old table is missing. So stale ALTER_TABLE RENAME events could incorrectly remove the new table or add the old table. The other case is in the fallback invalidation added in IMPALA-13989 that handles rename failure inside catalog (but succeeds in HMS). The createEventId is also set as -1. This patch fixes these by always setting a correct/meaningful createEventId. When fetching the ALTER_TABLE event fails, we try to use the event id before the HMS operation. It could be a little bit stale but much better than -1. Modified CatalogServiceCatalog#isEventProcessingActive() to just check if event processing is enabled and renamed it to isEventProcessingEnabled(). Note that this method is only used in DDLs that check their self events. We should allow these checks even when EventProcessor is not in the ACTIVE state. So when EventProcessor is recovered, fields like createEventId in tables are still correct. Removed the code of tracking in-flight events at the end of rename since the new table is in unloaded state and only the createEventId is useful. The catalog version used is also incorrect since it's not used in CatalogServiceCatalog#renameTable() so it doesn't make sence to use it. Removed the InProgressTableModification parameter of alterTableOrViewRename() since it's not used anymore. This patch also fixes a bug in getRenamedTableFromEvents() that it always returns the first event id in the list. It should use the rename event it finds. Tests - Added e2e test and ran it 40 times. Change-Id: Ie7c305e5aaafc8bbdb85830978182394619fad08 Reviewed-on: http://gerrit.cloudera.org:8080/23291 Reviewed-by: Riza Suminto <riza.suminto@cloudera.com> Reviewed-by: Michael Smith <michael.smith@cloudera.com> Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
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:
- Best of breed performance and scalability.
- Support for data stored in Apache Iceberg, 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
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.