Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Plain View
Sqoop >> mail # dev >> Review Request 13181: SQOOP-773 Sqoop2: Batch execution support for client commands


+
Abraham Elmahrek 2013-08-01, 00:40
+
Hari Shreedharan 2013-08-02, 06:02
+
Abraham Elmahrek 2013-08-05, 21:17
+
Abraham Elmahrek 2013-08-13, 21:30
+
Jarek Cecho 2013-09-03, 09:35
+
Abraham Elmahrek 2013-09-11, 00:35
+
rj.vasanthkumar@... 2013-09-17, 15:26
+
rj.vasanthkumar@... 2013-09-17, 15:31
+
rj.vasanthkumar@... 2013-09-24, 09:16
+
Abraham Elmahrek 2013-09-23, 23:18
Copy link to this message
-
Re: Review Request 13181: SQOOP-773 Sqoop2: Batch execution support for client commands


> On Sept. 17, 2013, 3:26 p.m., vasanthkumar wrote:
> >
>
> vasanthkumar wrote:
>     In Create connection, for sensitive information password can we have separate in next line? Instead of getting password from same command line.
>
> Abraham Elmahrek wrote:
>     I'm not sure I entirely understand. If there are multiple sensitive fields, then there would be multiple next lines? How would we know which goes where? Also, since this is batch execution mode, then it wouldn't make sense to stop the execution of the commands to ask for inputs.
>
> vasanthkumar wrote:
>     create connection --cid 1 --name mysql-test --connector-connection-jdbcDriver com.mysql.jdbc.Driver --connector-connection-connectionString jdbc:mysql://hue.ent.cloudera.com/test --connector-connection-username root --connector-connection-password root
>    
>     Above command, password is visible to user. So like in version 1.4.x, use -P for getting password from console.
>
>
> Jarek Cecho wrote:
>     That is very good catch Vasanth! Indeed you are right, the password will be clearly visible in plaintext on the command line which might be seen similar to parameter --password in Sqoop 1.x. Nevertheless I feel that there is a huge difference as Sqoop2 still have the interactive mode where the password is correctly hidden. The JIRA seems to be proposing fully batch mode that can be for example used from within scripts, so reading data from stdin do not appear to be an option in this case. Having said that there is a secure way how to enter sensitive information, do you think that current approach is sensible?

I see what you're saying now. I do agree with Jarcec on his points though. Ideally, connections would be reused so that sensitive information shouldn't less frequently.

One scenario I can imagine is where there are several users that each have their own credentials to a database (which is achievable through LDAP). Then, a sequence of sqoop commands to create a connection and a basic import job to a sandboxed area would be nice. This is treading on scripting territory though, which probably belongs in a shell script of some kind.
- Abraham
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/13181/#review26175
-----------------------------------------------------------
On Sept. 23, 2013, 11:48 p.m., Abraham Elmahrek wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13181/
> -----------------------------------------------------------
>
> (Updated Sept. 23, 2013, 11:48 p.m.)
>
>
> Review request for Sqoop, Hari Shreedharan and Jarek Cecho.
>
>
> Bugs: SQOOP-773
>     https://issues.apache.org/jira/browse/SQOOP-773
>
>
> Repository: sqoop-sqoop2
>
>
> Description
> -------
>
> commit 080ced16578c1d95015ce3e99b4335beb465861a
> Author: Abraham Elmahrek <[EMAIL PROTECTED]>
> Date:   Tue Aug 13 14:14:06 2013 -0700
>
>     SQOOP-773 Sqoop2: Batch execution support for client commands
>    
>     Separated options into two groups: fixed and dynamic options.
>     Fixed options (IE: connector ID) come first and are used to select
>     what options should be used in dynamic options. Dynamic options
>     are automatically created based on forms selected from fixed options.
>     The keys for these options take on the form "<prefix>-<form name>-<input-name>".
>
> :100644 100644 980a908... a7e7e7d... M  shell/src/main/java/org/apache/sqoop/shell/CloneCommand.java
> :100644 100644 856abaa... 2c2869c... M  shell/src/main/java/org/apache/sqoop/shell/CloneConnectionFunction.java
> :100644 100644 3e23025... dd2eb2b... M  shell/src/main/java/org/apache/sqoop/shell/CloneJobFunction.java
> :100644 100644 e62ce08... 9ad007b... M  shell/src/main/java/org/apache/sqoop/shell/CreateCommand.java
> :100644 100644 5fbf0a3... 973fd53... M  shell/src/main/java/org/apache/sqoop/shell/CreateConnectionFunction.java
+
Jarek Cecho 2013-09-24, 15:44
+
Abraham Elmahrek 2013-09-23, 23:48
+
Jarek Cecho 2013-09-24, 22:27
+
Jarek Cecho 2013-09-26, 15:55
+
Abraham Elmahrek 2013-09-26, 09:33
+
Abraham Elmahrek 2013-09-27, 18:30
+
Abraham Elmahrek 2013-10-14, 19:05
+
Jarek Cecho 2013-10-15, 20:51
+
Jarek Cecho 2013-10-15, 20:51
+
Abraham Elmahrek 2013-10-15, 22:56
+
Jarek Cecho 2013-10-16, 21:23
+
Jarek Cecho 2013-10-11, 20:02
+
Abraham Elmahrek 2013-10-14, 18:03
+
Jarek Cecho 2013-10-14, 14:52
+
Abraham Elmahrek 2013-10-13, 20:23
+
Jarek Cecho 2013-10-15, 17:13