[
https://issues.apache.org/jira/browse/HIVE-18973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498402#comment-16498402
]
Eugene Koifman commented on HIVE-18973:
---------------------------------------
ok, I did't see the last comment here so I reviewed the current patch.
In general, it looks like whenever there is db/table in a RDBMS table, you
added a catalog field. That makes sense.
Could you elaborate on the cross catalog locking restriction. How/where would
that be enforced. I assume it means a query/transaction cannot use resources
from multiple catalogs?
I saw a number of places where the code checks if catalog is set and if not
uses default one. This seems like it can lead to difficult bugs. I think
MetaStoreUtils.getDefaultCatalog(conf) should be used as little as possible
(especially in TxnHandler, but probably in other places as well).
> Make transaction system work with catalogs
> ------------------------------------------
>
> Key: HIVE-18973
> URL: https://issues.apache.org/jira/browse/HIVE-18973
> Project: Hive
> Issue Type: Sub-task
> Components: Metastore
> Affects Versions: 3.0.0
> Reporter: Alan Gates
> Assignee: Alan Gates
> Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-18973.patch
>
>
> The transaction tables need to understand catalogs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
