Behavioral changes denote a marked change in behavior from the previously released
version to this version of Apache Impala.
Behavioral Changes in Cloudera Runtime 7.3.1.400 SP2
There are no behavioral changes in this release.
Behavioral Changes in Cloudera Runtime 7.3.1.300 SP1 CHF 1
- Summary:
- Impala Query Analysis Behavior with Ranger.
- Previous behavior:
- Impala previously verified WRITE access for the service user on HDFS
table/partition(s) during query analysis of
INSERT
and LOAD
DATA
statements in legacy catalog mode. Permissions were computed based on HDFS
settings, including ACLs, when tables and partitions were instantiated.
- New behavior:
- To address performance concerns, HDFS permissions are now skipped
during query analysis. The service user is assumed to have
READ_WRITE
access
to all HDFS paths associated with the target table when Ranger is enabled. Ranger policies
remain enforced during query execution for INSERT
and LOAD
DATA
statements, ensuring security compliance.Apache Jira: IMPALA-11871
- Summary:
- Expression rewrite behavior for Hive views with auto-generated column
aliases.
- Previous behavior:
- Impala attempted to simplify
CAST
expressions for
all columns, including those with Hive auto-generated aliases (such as _c0), introduced by the
SimplifyCastExprRule
optimization in IMPALA-10836. In views created in Hive
without explicit column aliases, this could lead to AnalysisException errors during query
execution. For example, a view using CAST
on a column labeled as _c0 might
fail
with:AnalysisException: Could not resolve column/field reference:
'failing_view._c0'
- New behavior:
- Impala now skips rewriting expressions that are associated with Hive
auto-generated column aliases (for example, _c0, _c1, etc.). This preserves the correct column
mapping across nested views and avoids errors during query analysis. This change allows
queries to succeed without requiring you to explicitly rename columns in Hive
views.
Apache Jira: IMPALA-11871
Behavioral Changes in Cloudera Runtime 7.3.1.200 SP1
There are no behavioral changes in this release.
Behavioral Changes in Cloudera Runtime 7.3.1.100 CHF 1
There are no behavioral changes in this release.
Behavioral Changes in Cloudera Runtime 7.3.1
- Summary:
- Skips scheduling runtime filters for PK-FK joins when the build scan
has no predicate filter, the join is a full table scan, and the bloom filter has a high false
positive probability.
- Previous behavior:
- Runtime filters were scheduled for all PK-FK joins, regardless of
effectiveness.
- New behavior:
- Filters are skipped for PK-FK joins when the build scan is a full
table scan without filters, and the bloom filter has a high false positive probability,
improving performance. For more details see, Skip Scheduling Bloom Filter
Apache
Jira:
IMPALA-12357
- Summary:
- Skips LZ4 compression when sending row batches within the same
process to improve efficiency.
- Previous behavior:
- Row batches were serialized, compressed, sent through KRPC, and then
decompressed, even when the sender and receiver were in the same process.
- New behavior:
- LZ4 compression is skipped for row batches sent within the same
process, reducing unnecessary work and improving performance.
Apache Jira:
IMPALA-12430