You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/06/23 04:00:01 UTC
[jira] [Commented] (IMPALA-10361) Supported using filed id to
resolve columns for Iceberg tables
[ https://issues.apache.org/jira/browse/IMPALA-10361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17367849#comment-17367849 ]
ASF subversion and git services commented on IMPALA-10361:
----------------------------------------------------------
Commit c591b846c7956ec8eb0b1479237ac251a9d8ffed in impala's branch refs/heads/master from Zoltan Borok-Nagy
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=c591b84 ]
IMPALA-10166 (part 2): Enable DROP and CHANGE column
IMPALA-10166 (part 1) already added the necessary code for
DROP and CHANGE COLUMN, but disabled those stmts because to correctly
support schema evolution we had to wait for column resolution
by Iceberg field id.
Since then IMPALA-10361 and IMPALA-10485 added support for field-id
based column resolution for Parquet and ORC as well.
Hence this patch enables DROP and CHANGE column ALTER TABLE
statements. We still disallow REPLACE COLUMNS because it doesn't
really make sense for Iceberg tables as it basically makes all
existing data inaccessible.
Changing DECIMAL columns are still disabled due to IMPALA-7087.
Testing:
* added e2e tests
Change-Id: I9b0d1a55bf0ed718724a69b51392ed53680ffa90
Reviewed-on: http://gerrit.cloudera.org:8080/17593
Reviewed-by: Impala Public Jenkins <im...@cloudera.com>
Tested-by: Zoltan Borok-Nagy <bo...@cloudera.com>
> Supported using filed id to resolve columns for Iceberg tables
> --------------------------------------------------------------
>
> Key: IMPALA-10361
> URL: https://issues.apache.org/jira/browse/IMPALA-10361
> Project: IMPALA
> Issue Type: Sub-task
> Components: Frontend
> Reporter: Sheng Wang
> Assignee: Sheng Wang
> Priority: Major
>
> Impala now supported POSITION and NAME to resolve columns, we can decide which way to use through query option 'PARQUET_FALLBACK_SCHEMA_RESOLUTION'. Since Iceberg table has field_id for each column, we should also supported resolve column by field id.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org