[jira] [Resolved] (KUDU-3468) Support {INSERT,UPSERT}_IGNORE in the 'kudu table copy' CLI tool

["Alexey Serbin (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KUDU-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Serbin resolved KUDU-3468.
---------------------------------
    Fix Version/s: 1.17.0
       Resolution: Fixed

Implemented:
* main: https://github.com/apache/kudu/commit/adc1cc64e3fa26227b1400ec5a7ede870f03d39d
* branch-1.17.x: https://github.com/apache/kudu/commit/261ce7daa83a716c2ad9b960b9c904f11bdb7a68

> Support {INSERT,UPSERT}_IGNORE in the 'kudu table copy' CLI tool
> ----------------------------------------------------------------
>
>                 Key: KUDU-3468
>                 URL: https://issues.apache.org/jira/browse/KUDU-3468
>             Project: Kudu
>          Issue Type: Improvement
>          Components: CLI
>            Reporter: Alexey Serbin
>            Assignee: Alexey Serbin
>            Priority: Major
>              Labels: supportability, usability
>             Fix For: 1.17.0
>
>
> It would be great to make {{kudu table copy}} CLI tool supporting {{INSERT_IGNORE}} and {{UPSERT_IGNORE}} operations.  Having that is necessary to make copying tables from one cluster to another re-entrant, i.e. make it possible to restart the script/command (without preliminary resetting/cleaning the destination table) if copying failed in the middle due to some transient error.
> Another approach might be starting a multi-row transaction in the destination Kudu cluster, so in case of a failure all the inserted rows rolled back, but that should be handled as a separate issue.



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