[
https://issues.apache.org/jira/browse/IMPALA-12857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867965#comment-17867965
]
ASF subversion and git services commented on IMPALA-12857:
----------------------------------------------------------
Commit 05585c19bfcc235ab9d7574c970db04125fb9743 in impala's branch
refs/heads/master from Noemi Pap-Takacs
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=05585c19b ]
IMPALA-12857: Add flag to enable merge-on-read even if tables are configured
with copy-on-write
Impala can only modify an Iceberg table via 'merge-on-read'. The
'iceberg_always allow_merge_on_read_operations' backend flag makes it
possible to execute 'merge-on-read' operations (DELETE, UPDATE, MERGE)
even if the table property is 'copy-on-write'.
Testing:
- custom cluster test
- negative E2E test
Change-Id: I3800043e135beeedfb655a238c0644aaa0ef11f4
Reviewed-on: http://gerrit.cloudera.org:8080/21578
Reviewed-by: Daniel Becker <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Add flag to enable merge-on-read even if tables are configured with
> copy-on-write
> ---------------------------------------------------------------------------------
>
> Key: IMPALA-12857
> URL: https://issues.apache.org/jira/browse/IMPALA-12857
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend
> Reporter: Zoltán Borók-Nagy
> Assignee: Noemi Pap-Takacs
> Priority: Major
> Labels: impala-iceberg
>
> Impala can only modify a table via 'merge-on-read'. It raises an error if
> users want to modify a table that is configured with 'copy-on-write'.
> We could add a backend flag to relax this restriction, i.e. enable
> 'merge-on-read' operations (DELETE, UPDATE, MERGE) even if the table property
> is 'copy-on-write'.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
