sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Kemper (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SQOOP-3183) Sqoop1 (doc import + --incremental lastmodified) does not cover the --merge-key option
Date Sat, 06 May 2017 16:18:04 GMT
Markus Kemper created SQOOP-3183:
------------------------------------

             Summary: Sqoop1 (doc import + --incremental lastmodified) does not cover the
--merge-key option
                 Key: SQOOP-3183
                 URL: https://issues.apache.org/jira/browse/SQOOP-3183
             Project: Sqoop
          Issue Type: Bug
            Reporter: Markus Kemper


Sqoop1 (doc import + --incremental lastmodified) does not cover the --merge-key option

===========
https://sqoop.apache.org/docs/1.4.6/SqoopUserGuide.html#_incremental_imports
7.2.10. Incremental Imports
Table 5. Incremental import arguments:

Sqoop supports two types of incremental imports: append and lastmodified. You can use the
--incremental argument to specify the type of incremental import to perform.
--check-column (col)
--incremental (mode)
--last-value (value)

An alternate table update strategy supported by Sqoop is called lastmodified mode. You should
use this when rows of the source table may be updated, and each such update will set the value
of a last-modified column to the current timestamp. Rows where the check column holds a timestamp
more recent than the timestamp specified with --last-value are imported.
===========



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message