Review Board 1.7.22


Fix for SQOOP-1224

Review Request #15222 - Created Nov. 5, 2013 and updated

Venkat Ranganathan
SQOOP-1224
Reviewers
Sqoop
sqoop-trunk
When we use wallet based authentication (which enables secure external authentication in Oracle), the Sqoop jobs fail.   The reason for this is that in a wallet based authentication, the username, password and DB information are hidden and only a service is exposed.   So, all queries to which we pass the owner as a parameter will fail.  This patch adds the ability to substitute the logged on Oracle user if the username is not provided (as in wallet based implementations), but can also be used for other SSO mechanisms
Added one test to validate the query to get the current logged on user.   All tests pass.  No new checkstyle violations introduced
Total:
1
Open:
1
Resolved:
0
Dropped:
0
Status:
From:
Ship it!
Posted (Nov. 5, 2013, 10:19 p.m.)

   

  
+1

I believe that this will be even better as it will overcome the need to specify the user name with correct case on the command line!
Jarcec