About reddy_gayathri

reddy_gayathri · ‎11-22-2018

using PUT command, need to submit the curl twice. There is "negotiate" curl command which does the same in single submission. curl --negotiate -u : -L "http://namenode:50070/webhdfs/v1/user/username/余宗阳视频审核稿-1024.docx?op=CREATE&user.name=username" -T 余宗阳视频审核稿-1024.docx

reddy_gayathri · ‎11-22-2018

I found the root cause of the issue. Should use namenode with 50070 port. I was using edge node and hence the failure. Thanks!

reddy_gayathri · ‎11-21-2018

After encoding it is working for me. But the first command, it's still throwing the error "illegal character found at index 62". 62 is where the filename will start in the destination path. i checked the $LANG, and it is UTF-8. What was the exact output for you when executed the first curl without encoding?

reddy_gayathri · ‎11-21-2018

@Jagadeesan A S That's working thanks! I am trying to put the same file to hdfs using Curl via webhdfs and getting error ">HTTP Status 500 - Illegal character in path at index " curl -i -H 'content-type:application/octet-stream' -H 'charset:UTF-8' -X PUT -T '余宗阳视频审核稿-1024.docx' 'http://hostname:14000/webhdfs/v1/user/username/余宗阳视频审核稿-1024.docx?op=CREATE&data=true&user.name=username&overwrite=true' Any other header to be passed to recognize the chinese character here?

reddy_gayathri · ‎11-20-2018

I am trying to put a file in hadoop with the filename in chinese characters. file: 余宗阳视频审核稿-1024.docx but the file name is looking vaguely in hadoop as Óà×ÚÑôÊÓÆµÉóºË¸å-1024.docx Any hints to solve this issue?

reddy_gayathri · ‎07-17-2018

Matt, if you have the detailed document on importing data from Salesforce to Hadoop using nifi, please share.

reddy_gayathri · ‎04-17-2017

> I have millions of records in each table and hundreds of tables, so first option might not be optimal for big tables. > will try out the other options thank you

reddy_gayathri · ‎04-13-2017

Hi Is there a way to compare the whole data of a table in hive and the same table in Oracle?

reddy_gayathri · ‎12-02-2016

Sqoop import failing with "exception: Java Heap space" when there are no records in Oracle source table. I used a fetchsize of 75000 in sqoop import. sqoop import successfully ran when I removed fetch-size 75000 though no records in source table. I am standardizing the Sqoop import job which can be used for many other tables. And suppose in production, if there are no records, job should not fail. how to avoid this situation. And why it is failing when using bigger fetch-size. Thanks

reddy_gayathri · ‎11-25-2016

Yes, that worked. after giving SELECT_CATALOG_ROLE privileges, direct option is working.

Online	Offline
Last Visited	‎12-15-2020 12:33 PM

Member Since	‎07-28-2016 12:13 PM
Last Visited	‎12-15-2020 12:33 PM
Posts	27
Kudos received	8

Cloudera Community

Re: Unable to view/see the filename correctly when...

Re: Unable to view/see the filename correctly when...

Re: Unable to view/see the filename correctly when...

Re: Unable to view/see the filename correctly when...

Unable to view/see the filename correctly when sto...

Re: Salesforce integration with Hortonworks Data F...

Re: Compare Tables between Hive and Oracle

Compare Tables between Hive and Oracle

Sqoop import failing with "exception: Java Heap sp...

Re: Sqoop import with --direct is not working for ...