You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2015/03/04 05:46:04 UTC

[jira] [Commented] (SQOOP-2168) Incremental imports using metastore need to be parameterizable

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

Jarek Jarcec Cecho commented on SQOOP-2168:
-------------------------------------------

I believe that you should be simply do something like:

{code}
sqoop job --exec myAwesome job -- --parameter NEW_VALUE
{code}

To override any stored parameter.

> Incremental imports using metastore need to be parameterizable
> --------------------------------------------------------------
>
>                 Key: SQOOP-2168
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2168
>             Project: Sqoop
>          Issue Type: Bug
>          Components: metastore
>    Affects Versions: 1.4.5
>            Reporter: Mark Grover
>
> I have a use-case where I want to be able to add a new partition on every run of an incremental import job. However, the parameters of this import job are saved when I create and job and store it in the metastore.
> I want to pass a parameter to this job on every run about the partition spec where I want the data to get imported to but I wasn't able to find a way to supply such a parameter when executing such a saved job.



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