[
https://issues.apache.org/jira/browse/IMPALA-10947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715995#comment-17715995
]
ASF subversion and git services commented on IMPALA-10947:
----------------------------------------------------------
Commit 422006a8090bb7ee4576f4dbb2d6cbd3152ffded in impala's branch
refs/heads/master from Tamas Mate
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=422006a80 ]
IMPALA-11950: Planner change for Iceberg metadata querying
This commit extends the planner with IcebergMetadataScanNode which will
be used to scan Iceberg metadata tables (IMPALA-10947). The scan node is
only implemented on the frontend side in this patch, the backend part
will be developed in IMPALA-11996.
To avoid executing the plan there is a hardcoded condition, it is after
the explain part, so the change remains testable with EXPLAIN queries.
Testing:
- Added planner tests
Change-Id: I3675d7a57ca570bfec306798589b5ef6aa34b5c6
Reviewed-on: http://gerrit.cloudera.org:8080/19547
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> SQL support for querying Iceberg metadata
> -----------------------------------------
>
> Key: IMPALA-10947
> URL: https://issues.apache.org/jira/browse/IMPALA-10947
> Project: IMPALA
> Issue Type: New Feature
> Components: Frontend
> Reporter: Zoltán Borók-Nagy
> Assignee: Tamas Mate
> Priority: Major
> Labels: impala-iceberg
>
> HIVE-25457 added support for querying Iceberg table metadata to Hive.
> They support the following syntax:
> SELECT * FROM default.iceberg_table.history;
> Spark uses the same syntax: https://iceberg.apache.org/spark-queries/#history
> Other than "history", the following metadata tables are available in Iceberg:
> The following metadata tables are available in Iceberg:
> * ENTRIES,
> * FILES,
> * HISTORY,
> * SNAPSHOTS,
> * MANIFESTS,
> * PARTITIONS,
> * ALL_DATA_FILES,
> * ALL_MANIFESTS,
> * ALL_ENTRIES
> Impala currently only supports "DESCRIBE HISTORY <tbl>". The above SELECT
> syntax would be more convenient for the users, also it would be more flexible
> as users could easily define filters in WHERE clauses. And of course we would
> be consistent with other engines.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
