You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Naveen Gangam (Jira)" <ji...@apache.org> on 2021/04/02 18:52:00 UTC

[jira] [Created] (HIVE-24970) Reject location and managed locations in DDL for REMOTE databases.

Naveen Gangam created HIVE-24970:
------------------------------------

             Summary: Reject location and managed locations in DDL for REMOTE databases.
                 Key: HIVE-24970
                 URL: https://issues.apache.org/jira/browse/HIVE-24970
             Project: Hive
          Issue Type: Sub-task
          Components: HiveServer2
    Affects Versions: 4.0.0
            Reporter: Naveen Gangam
            Assignee: Naveen Gangam


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
(v8.3.4#803005)