hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanth Jayachandran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-19260) Streaming Ingest API doesn't normalize db.table names
Date Mon, 23 Apr 2018 04:10:00 GMT

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

Prasanth Jayachandran commented on HIVE-19260:
----------------------------------------------

is o1.getDbname() guaranteed to be non-null in LockComparator?

> Streaming Ingest API doesn't normalize db.table names
> -----------------------------------------------------
>
>                 Key: HIVE-19260
>                 URL: https://issues.apache.org/jira/browse/HIVE-19260
>             Project: Hive
>          Issue Type: Bug
>          Components: HCatalog, Streaming, Transactions
>    Affects Versions: 0.13
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>            Priority: Blocker
>         Attachments: HIVE-19260.01.patch
>
>
> Hive is case insensitive wrt db/table names.  These gets normalized to lower case for
SQL processing.
> When HiveEndPoint is created it uses db.table strings as is, and they end up propagated
this way to transaction metadata tables in the metastore via lock acquisition.  This makes
them look like different tables in Cleaner and lock manager.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message