hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <>
Subject [jira] [Work logged] (HIVE-15690) Speed up WebHCat DDL Response Time by Using JDBC
Date Tue, 16 Jun 2020 16:58:02 GMT


ASF GitHub Bot logged work on HIVE-15690:

                Author: ASF GitHub Bot
            Created on: 16/Jun/20 16:57
            Start Date: 16/Jun/20 16:57
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] commented on pull request #133:

   This pull request has been automatically marked as stale because it has not had recent
activity. It will be closed if no further activity occurs.
   Feel free to reach out on the list if the patch is in need of reviews.

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:

Issue Time Tracking

            Worklog Id:     (was: 446736)
    Remaining Estimate: 23h 50m  (was: 24h)
            Time Spent: 10m

> Speed up WebHCat DDL Response Time by Using JDBC
> ------------------------------------------------
>                 Key: HIVE-15690
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: WebHCat
>            Reporter: Amin Abbaspour
>            Assignee: Amin Abbaspour
>            Priority: Minor
>              Labels: easyfix, patch, performance, security
>   Original Estimate: 24h
>          Time Spent: 10m
>  Remaining Estimate: 23h 50m
> 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

View raw message