[
https://issues.apache.org/jira/browse/HIVE-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293816#comment-13293816
]
Carl Steinbach commented on HIVE-3121:
--------------------------------------
HiveDatabaseMetadata.getCatalogs() currently returns the list of
databases/schemas defined in the metastore, which is incorrect. In fact,
HiveDatabaseMetadata.getSchemas() should return this information, and
getCatalogs() should return an empty result set. Hive currently doesn't
implement the concept of a catalog, and instead borrowed MySQL's convention of
using both DATABASE and SCHEMA to identify the same class of catalog objects
that allow you to partition your tables into separate namespaces.
This blurb
(http://stackoverflow.com/questions/7942520/relationship-between-catalog-schema-user-and-database-instance)
probably does a better job of summarizing these relationships:
{quote}
In MySQL:
* server instance == catalog == set of schemas managed by same execution engine
* schema == database == a namespace within the server where tables are stored
* user == named account, who can connect to server and use objects in database
or in other dbs
* to identify any object you need (schema name + object name)
{quote}
> JDBC driver's getCatalogs() method returns schema/db information
> ----------------------------------------------------------------
>
> Key: HIVE-3121
> URL: https://issues.apache.org/jira/browse/HIVE-3121
> Project: Hive
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 0.9.0
> Reporter: Carl Steinbach
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
