[
https://issues.apache.org/jira/browse/HIVE-14116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Naveen Gangam resolved HIVE-14116.
----------------------------------
Resolution: Duplicate
Assignee: Naveen Gangam
Fix Version/s: 1.0.0
This appears to have been resolved via HIVE-8485. Please set
{{hive.metastore.orm.retrieveMapNullsAsEmptyStrings=true}} in the hive
configuration to get around this issue.
I have verified this with for the usecase in this jira. Closing this jira as
duplicate. Please re-open if you have questions or concerns. Thanks
> TBLPROPERTIES does not allow empty string values when Metastore is backed by
> Oracle database.
> ---------------------------------------------------------------------------------------------
>
> Key: HIVE-14116
> URL: https://issues.apache.org/jira/browse/HIVE-14116
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 1.1.0
> Reporter: Tony Hill
> Assignee: Naveen Gangam
> Fix For: 1.0.0
>
>
> DDL commands like:
> ALTER TABLE test SET TBLPROPERTIES('serialization.null.format'='');
> are silently ignored if the database backing Metastore is Oracle. This
> appears to be because Oracle treats an empty string as null.
> Unlike when using MySql, no entry is created in the TBL_PARAMS table.
> Steps to reproduce:
> Create a table with a string field.
> eg table mytable, field mystringfield.
> ALTER TABLE mytable SET TBLPROPERTIES('serialization.null.format'='');
> DESCRIBE FORMATTED mytable;
> with mysql backed Metastore, the entry will be displayed:
> serialization.null.format
> and an entry is created in the TBL_PARAMS for the parameter.
> With Oracle backed metastore, it is not, and no entry is created in
> TBL_PARAMS.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
