[jira] [Created] (IMPALA-12197) Time Travel Queries on Iceberg tables fail with "ERROR: IllegalArgumentException: null"

["Andrew Sherman (Jira)" <ji...@apache.org>]

Andrew Sherman created IMPALA-12197:
---------------------------------------

             Summary: Time Travel Queries on Iceberg tables fail with "ERROR: IllegalArgumentException: null"
                 Key: IMPALA-12197
                 URL: https://issues.apache.org/jira/browse/IMPALA-12197
             Project: IMPALA
          Issue Type: Bug
    Affects Versions: Impala 2.13.0
            Reporter: Andrew Sherman
            Assignee: Andrew Sherman


When using local catalog mode, if a runtime filter is being generated for a time travel iceberg table, then a query may fail with "ERROR: IllegalArgumentException: null"

In the planner an Iceberg table that is being accessed with Time Travel is represented by an IcebergTimeTravelTable object. This object represents a time-based variation on a base table. The  IcebergTimeTravelTable may represent a different schema from the base table, it does this by tracking its own set of Columns. As part of generating a runtime filter the isClusteringColumn() method is called on the table. IcebergTimeTravelTable was delegating this call to the base object. In local catalog mode this method is implemented by LocalTable which has a Preconditions check (an assertion) that the column parameter matches the stored column. In this case the check fails as the base table and time travel table have their own distinct set of column objects.

A possible fix is to have IcebergTimeTravelTable provide its own isClusteringColumn() method. For iceberg there are no clustering columns so this method simply returns false.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org