[
https://issues.apache.org/jira/browse/HIVE-29241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Butao Zhang updated HIVE-29241:
-------------------------------
Description:
HIVE-22995 introduced the concept of managedLocationUri. This means that
created databases will have two locations. The two properties
({*}metastore.warehouse.dir{*} and {*}metastore.warehouse.external.dir{*}) are
related to db's location.
To avoid disrupting the location of the current default catalog 'hive' (which
is controlled by the properties *metastore.warehouse.dir* and
{*}metastore.warehouse.external.dir{*}), the locations for newly created
catalogs should be separated from the default 'hive' catalog. Two new
parameters can be added, such as *metastore.warehouse.catalog.dir* and
{*}metastore.warehouse.catalog.external.dir{*}.
Moreover, the location for each newly created catalog should have the catalog
name appended at the end. For example, if *metastore.warehouse.catalog.dir* is
*hdfs://ns1/testdir,* then the location for a newly created catalog named
testcat would be {*}hdfs://ns1/testdir/testcat{*}. Consequently, the default
path for a database like testdb created under this catalog would be
{*}hdfs://ns1/testdir/testcat/testdb{*}.
was:
HIVE-22995 introduced the concept of managedLocationUri. This means that
created databases will have two locations.
Currently, when creating a catalog, there is only the location attribute,
without managedLocationUri. We should also add the managedLocationUri field to
the catalog, so that when users create a database from the new created catalog,
it can inherit the two locations from the catalog.
Additionally, to avoid disrupting the location of the current default catalog
'hive' (which is controlled by the properties *metastore.warehouse.dir* and
{*}metastore.warehouse.external.dir{*}), the locations for newly created
catalogs should be separated from the default 'hive' catalog. Two new
parameters can be added, such as *metastore.warehouse.catalog.dir* and
{*}metastore.warehouse.catalog.external.dir{*}.
Moreover, the location for each newly created catalog should have the catalog
name appended at the end. For example, if *metastore.warehouse.catalog.dir* is
*hdfs://ns1/testdir,* then the location for a newly created catalog named
testcat would be {*}hdfs://ns1/testdir/testcat{*}. Consequently, the default
path for a database like testdb created under this catalog would be
{*}hdfs://ns1/testdir/testcat/testdb{*}.
> The database's default location should be determined by its catalog's location
> ------------------------------------------------------------------------------
>
> Key: HIVE-29241
> URL: https://issues.apache.org/jira/browse/HIVE-29241
> Project: Hive
> Issue Type: Sub-task
> Components: Standalone Metastore
> Reporter: Butao Zhang
> Assignee: Butao Zhang
> Priority: Major
>
> HIVE-22995 introduced the concept of managedLocationUri. This means that
> created databases will have two locations. The two properties
> ({*}metastore.warehouse.dir{*} and {*}metastore.warehouse.external.dir{*})
> are related to db's location.
> To avoid disrupting the location of the current default catalog 'hive' (which
> is controlled by the properties *metastore.warehouse.dir* and
> {*}metastore.warehouse.external.dir{*}), the locations for newly created
> catalogs should be separated from the default 'hive' catalog. Two new
> parameters can be added, such as *metastore.warehouse.catalog.dir* and
> {*}metastore.warehouse.catalog.external.dir{*}.
> Moreover, the location for each newly created catalog should have the catalog
> name appended at the end. For example, if *metastore.warehouse.catalog.dir*
> is *hdfs://ns1/testdir,* then the location for a newly created catalog named
> testcat would be {*}hdfs://ns1/testdir/testcat{*}. Consequently, the default
> path for a database like testdb created under this catalog would be
> {*}hdfs://ns1/testdir/testcat/testdb{*}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
