hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sushanth Sowmyan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-8485) HMS on Oracle incompatibility
Date Tue, 13 Jan 2015 19:27:36 GMT

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

Sushanth Sowmyan commented on HIVE-8485:
----------------------------------------

@[~vikram.dixit] : Since this is an important robustness fix, I'd like to see this included
in 0.14.1 as well.

@[~ctang.ma] : Are you okay with this approach of fixing the robustness on our end?

@[~sershe] : Could you please review this patch?

> HMS on Oracle incompatibility
> -----------------------------
>
>                 Key: HIVE-8485
>                 URL: https://issues.apache.org/jira/browse/HIVE-8485
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>         Environment: Oracle as metastore DB
>            Reporter: Ryan Pridgeon
>            Assignee: Chaoyu Tang
>         Attachments: HIVE-8485.2.patch, HIVE-8485.patch
>
>
> Oracle does not distinguish between empty strings and NULL,which proves problematic for
DataNucleus.
> In the event a user creates a table with some property stored as an empty string the
table will no longer be accessible.
> i.e. TBLPROPERTIES ('serialization.null.format'='')
> If they try to select, describe, drop, etc the client prints the following exception.
> ERROR ql.Driver: FAILED: SemanticException [Error 10001]: Table not found <table name>
> The work around for this was to go into the hive metastore on the Oracle database and
replace NULL with some other string. Users could then drop the tables or alter their data
to use the new null format they just set.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message