hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naveen Gangam (Jira)" <>
Subject [jira] [Resolved] (HIVE-24970) Reject location and managed locations in DDL for REMOTE databases.
Date Tue, 06 Jul 2021 18:05:00 GMT


Naveen Gangam resolved HIVE-24970.
    Fix Version/s: 4.0.0
       Resolution: Fixed

Fix has been committed to master. Closing the jira. Thank you for the contribution [~dantongdong]

> Reject location and managed locations in DDL for REMOTE databases.
> ------------------------------------------------------------------
>                 Key: HIVE-24970
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: HiveServer2
>    Affects Versions: 4.0.0
>            Reporter: Naveen Gangam
>            Assignee: Dantong Dong
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>          Time Spent: 1h
>  Remaining Estimate: 0h
> This was part of the review feedback from Yongzhi. Creating a followup jira to track
this discussion.
> So, using DB connector for DB, will not create managed tables?
> @nrg4878 nrg4878 1 hour ago Author Member
> we don't support create/drop/alter in REMOTE databases at this point. the concepts of
managed vs external is not in the picture at this point. When we do support it, it will be
application to the hive connectors only (or other hive based connectors like AWS Glue)
> @nrg4878 nrg4878 2 minutes ago Author Member
> will file a separate jira for this. Basically, instead of ignoring the location and managedlocation
that may be specified for remote database, the grammer needs to not accept any locations in
the DDL at all.
> The argument is fair, why accept something we do not honor or entirely irrelevant for
such databases. However, this requires some thought when we have additional connectors for
remote hive instances. It might have some relevance in terms of security with Ranger etc.
> So will create new jira for followup discussion.

This message was sent by Atlassian Jira

View raw message