[
https://issues.apache.org/jira/browse/HIVE-19769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16502343#comment-16502343
]
Alan Gates commented on HIVE-19769:
-----------------------------------
Unfortunately I need the objects to be in the storage-api, as they need to be
used in ValidReaderWriteIdList.
> Create dedicated objects for DB and Table names
> -----------------------------------------------
>
> Key: HIVE-19769
> URL: https://issues.apache.org/jira/browse/HIVE-19769
> Project: Hive
> Issue Type: Sub-task
> Components: storage-api
> Affects Versions: 3.0.0
> Reporter: Alan Gates
> Assignee: Alan Gates
> Priority: Major
>
> Currently table names are always strings. Sometimes that string is just
> tablename, sometimes it is dbname.tablename. Sometimes the code expects one
> or the other, sometimes it handles either. This is burdensome for developers
> and error prone. With the addition of catalog to the hierarchy, this becomes
> even worse.
> I propose to add two objects, DatabaseName and TableName. These will track
> full names of each object. They will handle inserting default catalog and
> database names when those are not provided. They will handle the conversions
> to and from strings.
> These will need to be added to storage-api because ValidTxnList will use it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
