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.
>
>

Reply via email to