You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Wessel Valkenburg (Jira)" <ji...@apache.org> on 2020/07/23 09:45:00 UTC

[jira] [Created] (SQOOP-3479) Incremental import on existing table in Hive should throw exception if wrong file format is used

Wessel Valkenburg created SQOOP-3479:
----------------------------------------

             Summary: Incremental import on existing table in Hive should throw exception if wrong file format is used
                 Key: SQOOP-3479
                 URL: https://issues.apache.org/jira/browse/SQOOP-3479
             Project: Sqoop
          Issue Type: Improvement
          Components: sqoop2-client
    Affects Versions: 1.4.7
            Reporter: Wessel Valkenburg


Performing an incremental import on an existing table in Hive will corrupt that table if the import is performed with a different file format (for example textfile) than existing files in the table (for example parquet). Rather than corrupting the table, sqoop could check the file format and throw an error if the formats aren't the same.

 

This happens when you manually provide flags
{code:java}
--incremental append --check-column [somecolumn] --last-value [somevalue]{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)