Databases Reference
In-Depth Information
Solution
Sqoop offers two ways to run jobs from within the metastore without requiring any user
input. The first and more secure method is by using the parameter
--password-file
to pass in the file containing the password. The second, less secure method is to set the
property
sqoop.metastore.client.record.password
in the
sqoop-site.xml
to true:
<configuration>
...
<property>
<name>
sqoop.metastore.client.record.password
</name>
<value>
true
</value>
</property>
</configuration>
Discussion
Both available methods have their advantages and disadvantages. While using the pass‐
word file is considered safer, in order to secure it, you need to restrict access to the
password file. The Sqoop job will be executed with the permissions of the user running
the
--exec
operation rather than the user who created the saved job. You might need
to share the file between the two users.
The second method of storing the password inside the metastore is less secure. The
metastore is unencrypted, and thus anyone can easily retrieve your saved password.
This method might be feasible if you have a dedicated machine with very restricted user
access.
3.5. Overriding the Arguments to a Saved Job
Problem
You have a saved job that has been running fine. Recently it has become slower than
usual. You would like to get more details about the execution by adding the
--verbose
parameter.
Solution
You can add or override any parameters of the saved job when executing it. All you need
to do is add an extra
--
after the
--exec
command, followed by any additional param‐
eters you would like to add. For example, use the following command to add the
--verbose
parameter to the saved job
visits
:
sqoop job --exec visits -- --verbose
