Michael Smith created IMPALA-14638:
--------------------------------------
Summary: Iceberg metadata scan can still be scheduled to dedicated
executor
Key: IMPALA-14638
URL: https://issues.apache.org/jira/browse/IMPALA-14638
Project: IMPALA
Issue Type: Bug
Components: Backend
Affects Versions: Impala 4.4.0
Reporter: Michael Smith
IMPALA-12809 attempted to ensure fragments containing SCAN ICEBERG METADATA are
always scheduled to a coordinator. However that fix appears to be incomplete.
With {{start-impala-cluster.py --num_coordinators=1
--use_exclusive_coordinators}}, the following query still causes a metadata
scan to be scheduled to an executor and crashes it
{code}
CREATE TABLE default.iceberg_meta_join (foo BIGINT) STORED BY ICEBERG;
INSERT INTO default.iceberg_meta_join (foo) VALUES (1);
WITH meta_union AS (
SELECT 1 as snapshot_id FROM default.iceberg_meta_join.snapshots
UNION
SELECT 1 as snapshot_id FROM default.iceberg_meta_join.snapshots)
SELECT * FROM default.iceberg_meta_join AS t
INNER JOIN meta_union ON t.foo = meta_union.snapshot_id;
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
