Thanks for the reply. I have already seen the same in 5.3 and working on to use this.
Thanks, Jilani On Sun, Jan 18, 2015 at 1:48 AM, Jarek Jarcec Cecho <[email protected]> wrote: > Hi Jilani, > asking distribution specific questions is better on forums for given > distribution - for example cdh-user [1] mailing list or Cloudera forums [2]. > > For your convenience I’ve took a look and both SQOOP-1471 and HADOOP-10607 > are part of CDH 5.3.0 already. > > Jarcec > > Links: > 1: https://groups.google.com/a/cloudera.org/forum/#!forum/cdh-user > 2: http://community.cloudera.com/ > > > On Jan 14, 2015, at 7:26 PM, Venkat Ranganathan < > [email protected]> wrote: > > > > Unfortunately I don't have access to Cloudera 5.3. So can't say one > way or another on that. > > > > The Sqoop options are already in the documentation. The > CredentialProvider usage is documented as part of Hadoop 2.6.0 (as > mentioned in the Sqoop doc) > > > > Please see > http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/CommandsManual.html#credential > regarding setting up the credential provider > > > > Thanks > > > > Venkat > > ________________________________________ > > From: Jilani Shaik <[email protected]> > > Sent: Wednesday, January 14, 2015 11:37 AM > > To: [email protected] > > Subject: Re: encrypted password in command line i.e ("password") simialr > to "password-file" > > > > Hi Venkat, > > > > Thanks for this, I have also seen this solution(I think it is implemented > > by you), but we are using the cloudera 5.3 and I have verified that this > is > > coming with Hadoop 2.5. > > > > Please let me know how can I use this with cloudera 5.3. Also I did not > > find the usage documentation for this feature. Please provide URLs for > the > > same. > > > > > > Please suggest. > > > > Thanks, > > Jilani > > > > > > On Wed, Jan 14, 2015 at 2:12 PM, Venkat Ranganathan < > > [email protected]> wrote: > > > >> We added ‹password-alias option that makes use of the Hadoop 2.6 > >> CredentialProvider API - Please see SQOOP-1471. You need to use Hadoop > >> 2.6.0 for this (or if you use a vendor distribution, you need something > >> that is based on Hadoop 2.6.0) to use this feature > >> > >> Thanks > >> > >> Venkat > >> > >> On 1/14/15, 10:07 AM, "Jilani Shaik" <[email protected]> wrote: > >> > >>> Hi, > >>> > >>> I have seen the feature encrypted password in password-file in " > >>> https://issues.apache.org/jira/browse/SQOOP-1223"; in Sqoop 1223 JIRA > >>> issue. > >>> > >>> Please let me know whether the same is supported without password-file. > >>> > >>> As we have lot of sqoop imports using oozie workflow and there we are > >>> reading all the passwords from common property file. So for us instead > of > >>> using the password-file, common properties with encrypted password is > >>> suitable. > >>> > >>> > >>> Please let me know if you need any questions to understand my > requirement. > >>> > >>> Please suggest. > >>> > >>> > >>> Thanks, > >>> Jilani > >>> > >>> -- > >>> CONFIDENTIALITY NOTICE > >>> NOTICE: This message is intended for the use of the individual or > entity > >>> to > >>> which it is addressed and may contain information that is confidential, > >>> privileged and exempt from disclosure under applicable law. If the > reader > >>> of this message is not the intended recipient, you are hereby notified > >>> that > >>> any printing, copying, dissemination, distribution, disclosure or > >>> forwarding of this communication is strictly prohibited. If you have > >>> received this communication in error, please contact the sender > >>> immediately > >>> and delete it from your system. Thank You. > >> > >> > > > > -- > > CONFIDENTIALITY NOTICE > > NOTICE: This message is intended for the use of the individual or entity > to > > which it is addressed and may contain information that is confidential, > > privileged and exempt from disclosure under applicable law. If the reader > > of this message is not the intended recipient, you are hereby notified > that > > any printing, copying, dissemination, distribution, disclosure or > > forwarding of this communication is strictly prohibited. If you have > > received this communication in error, please contact the sender > immediately > > and delete it from your system. Thank You. > >
