[ 
https://issues.apache.org/jira/browse/HIVE-15690?focusedWorklogId=450148&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-450148
 ]

ASF GitHub Bot logged work on HIVE-15690:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 24/Jun/20 00:28
            Start Date: 24/Jun/20 00:28
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] closed pull request #133:
URL: https://github.com/apache/hive/pull/133


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 450148)
    Remaining Estimate: 23h 40m  (was: 23h 50m)
            Time Spent: 20m  (was: 10m)

> Speed up WebHCat DDL Response Time by Using JDBC
> ------------------------------------------------
>
>                 Key: HIVE-15690
>                 URL: https://issues.apache.org/jira/browse/HIVE-15690
>             Project: Hive
>          Issue Type: Improvement
>          Components: WebHCat
>            Reporter: Amin Abbaspour
>            Assignee: Amin Abbaspour
>            Priority: Minor
>              Labels: easyfix, patch, performance, pull-request-available, 
> security
>   Original Estimate: 24h
>          Time Spent: 20m
>  Remaining Estimate: 23h 40m
>
> WebHCat launches new hcat scripts for each DDL call which makes it unsuitable 
> for interactive REST environments.
> This change to speed up /ddl query calls by running them over JDBC connection 
> to Hive thrift server.
> Also being JDBC connection, this is secure and compatible with all access 
> policies define in Hive server2. User does not have metadata visibility over 
> other databases (which is the case in hcat mode.)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to