sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bohdar Herman (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SQOOP-3005) Sqoop lastmodified - custom upper bound
Date Fri, 02 Sep 2016 18:52:20 GMT
Bohdar Herman created SQOOP-3005:
------------------------------------

             Summary: Sqoop lastmodified - custom upper bound
                 Key: SQOOP-3005
                 URL: https://issues.apache.org/jira/browse/SQOOP-3005
             Project: Sqoop
          Issue Type: Wish
            Reporter: Bohdar Herman


>From what I understand, for the lastmodified update method, Sqoop selects records where
timestamp_column >= last modified timestamp and timestamp column < current_time. Is
there a way to customize that current_time upper bound? I'd like to do something like current_time
- 1 hour.
 
We have transactions being created on one server, then replicated to another server, then
Sqooped from there. I noticed some missing data in our cluster and I believe replication delay
is the cause. This new feature would be a great way to work around the replication delay.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message