You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "simran (JIRA)" <ji...@apache.org> on 2016/05/15 17:41:12 UTC

[jira] [Commented] (AMBARI-15106) Ambari should manage Sqoop metastore to facilitate incremental loads

    [ https://issues.apache.org/jira/browse/AMBARI-15106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15283888#comment-15283888 ] 

simran commented on AMBARI-15106:
---------------------------------

Would be very helpful. Infact I have not yet figured out a workaround for this. Would be great if someone could please share so.

> Ambari should manage Sqoop metastore to facilitate incremental loads
> --------------------------------------------------------------------
>
>                 Key: AMBARI-15106
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15106
>             Project: Ambari
>          Issue Type: Improvement
>            Reporter: Vlad
>
> Sqoop metastore is needed to enable incremental import jobs executed through Oozie. This metastore should be managed (install/start/stop/monitor) by Ambari.
> Sqoop incremental import jobs require --last-value parameter.   So that a user doesn't have to remember the parameter after each Sqoop execution a Sqoop job can be saved to the metastore where this parameter is remembered.  With out a central metastore Sqoop saves the data to $HOME/.sqoop/ and that does not work when executing a Sqoop job from Oozie.



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