Thanks Jarcec for guiding.  

Velmurugan
 This issue was fixed in the Teradata connector 1.3.3 version which is 
available as a add on for HDP 2.1

Venkat




On 2/26/15, 11:17 AM, "[email protected]" <[email protected]> wrote:

>[Looping in user list back, please do not remove it]
>
>It seems that this connector have not been updated to not put the 
>password into job conf yet. I would suggest to bring this issue to vendor 
>specific forums to see when this will get fixed.
>
>Jarcec
>
>> On Feb 26, 2015, at 10:06 AM, velmurugan vinayakam 
>><[email protected]> wrote:
>> 
>> Thanks Jarcec for your response!!!
>> 
>> im using hortonworks-teradata-connector-1.0.9.1.3.3.0-60.jar based out 
>>of teradata-connector-1.0.9.jar
>> Below is the sqoop Command. Log file attached
>>    /home/user/sqoop/sqoop-1.4.4.bin__hadoop-1.0.0/bin/sqoop import \
>>     -libjars $LIB_JARS \
>>     -Dteradata.db.input.job.type=hdfs \
>>     --connect jdbc:teradata://hostname/Database=USER_DB \
>>     --connection-manager org.apache.sqoop.teradata.TeradataConnManager \
>>     --username td_user \
>>     --password-file "/tmp/sqoop_user/.password" \
>>     --target-dir /user/hive/warehouse/table1 \
>>      --table  USER_DB.Testtable1 \
>>      -m 1 --verbose
>>          
>> 
>> On Thu, Feb 26, 2015 at 9:21 AM, Jarek Jarcec Cecho <[email protected]> 
>>wrote:
>> What connector are you using? This is indeed fixed in Sqoop core and 
>>all connectors that we ship by default, but various external connectors 
>>might be using their own way how to serialize password to mapreduce job.
>> 
>> (Sqoop command line and log generated with —verbose will help us answer 
>>this question)
>> 
>> Jarcec
>> 
>> > On Feb 26, 2015, at 8:19 AM, velmurugan vinayakam 
>><[email protected]> wrote:
>> >
>> > Hi,
>> >
>> > I see in some previous posts that this issue is resolved in 1.4.4 .Im 
>>using 1.4.4 but the password is still exposed in job conf even when the 
>>password is passed through --password-file. Please let me know if this 
>>issue is still there in Sqoop 1.We will not be able to migrate to sqoop2 
>>at this point.is there any workaround for masking the passwords in 
>>sqoop1?
>> >
>> > Any help will be appreciated. Thanks!!!
>> 
>> 
>> <sqooplog.txt>
>

Reply via email to