hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zoltan Haindrich (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-19769) Create dedicated objects for DB and Table names
Date Mon, 11 Jun 2018 16:59:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-19769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508373#comment-16508373
] 

Zoltan Haindrich commented on HIVE-19769:
-----------------------------------------

It's great to see this object; I've saw some problematic places which have became somewhat
fragile because of the default database...I think it would be good to move it forward to pass
TableName objects around instead of 2-3 strings...
+1 

> 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
>         Attachments: HIVE-19769.patch
>
>
> 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)

Mime
View raw message