Know more about the behavioral changes in cumulative hotfix 7 for 7.1.9
SP1.
Impala
- 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
