Thanks a lot. I will try to test it soon.

Regards,


Ahmed Kamal
MTS in Data Science
Email: [email protected]<mailto:[email protected]>


From: Amin Abbaspour <[email protected]>
Reply-To: "[email protected]" <[email protected]>
Date: Friday, January 27, 2017 at 2:37 AM
To: "[email protected]" <[email protected]>
Subject: Re: Scaling HCatalog REST API

Hi Ahmed,

I've changed webhcat to use JDBC connectivity rather than running hcat command 
and it performs much faster.
There is ticket (https://issues.apache.org/jira/browse/HIVE-15690) and PR 
(https://github.com/apache/hive/pull/133) for that. Feel free to test it.

Kind regards,
Amin



On Thu, Jan 26, 2017 at 1:36 AM, Ahmed Kamal Abdelfatah 
<[email protected]<mailto:[email protected]>> wrote:
Hi folks,

I’m working on some workflow that needs to hit an API for fetching hive table 
schema.

Currently, I’m using HCatalog Tempelton API
"apiURL:50111/templeton/v1/ddl/database/dbName/table/tableName?user.name<http://user.name>=hive”
 but as the rate of requests is increasing (currently the max is 10 per second)

I get a lot of timeout from the API. I was looking to know how I can scale this 
API to be able to get better performance instead of increasing the timeout of 
course. Are there any params that needs tuning ? Should this be done on the 
metastore layer ? Thanks a lot.


Regards,


Ahmed Kamal
MTS Engineer in Data Science
Email: [email protected]<mailto:[email protected]>




--

Amin Abbaspour

Senior AWS Consultant


[http://strutdigital.com/strut_logo_sig.png]


Phone  +61 450 445 271

Email     [email protected]<mailto:[email protected]>

Website strutdigital.com<http://strutdigital.com/>

Twitter   @strutdigital<http://twitter.com/strutdigital>

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this email in error please notify the system manager. This 
message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system. If you are not the intended recipient you are 
notified that disclosing, copying, distributing or taking any action in 
reliance on the contents of this information is strictly prohibited.

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this email in error please notify the system manager. This 
message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system. If you are not the intended recipient you are 
notified that disclosing, copying, distributing or taking any action in 
reliance on the contents of this information is strictly prohibited.

Reply via email to