[
https://issues.apache.org/jira/browse/SQOOP-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055003#comment-14055003
]
Jarek Jarcec Cecho commented on SQOOP-1364:
-------------------------------------------
I believe that the observed behavior is fully expected and documented:
https://github.com/apache/sqoop/blob/trunk/conf/sqoop-site-template.xml#L115
You can either allow Sqoop to store the password in metastore (insecure) or use
{{--password-file}} instead.
> When we try to execute a saved Sqoop job, no matter what, it always prompts
> for a password
> ------------------------------------------------------------------------------------------
>
> Key: SQOOP-1364
> URL: https://issues.apache.org/jira/browse/SQOOP-1364
> Project: Sqoop
> Issue Type: Bug
> Components: tools
> Affects Versions: 1.4.3
> Reporter: Sai Karthik Ganguru
>
> When an already existing Sqoop job is executed, it always prompts for a
> password. Even if we include --password in the CLI:
> $sqoop job --exec PHL -- --password abcd
> *PHL is the stored Sqoop job name.
> After executing the above command, it prompts for a password and even if we
> enter some junk value (not necessarily the password) it continues to execute
> fine.
> Steps to be taken:
> Either it should not prompt for a password when we pass the --password
> parameter
> or
> If the Sqoop job was intended to prompt for a password always, then it should
> not take any junk value that is passed onto it.
> Note: If we can remove the prompt for a password when the --password option
> is used in the command, this will benefit people running Sqoop jobs through
> schedulers like Autosys (which will not be responsive to the password prompts
> that the Sqoop job throws).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
