[
https://issues.apache.org/jira/browse/HIVE-14322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390973#comment-15390973
]
Thejas M Nair commented on HIVE-14322:
--------------------------------------
Setting DN autocreate flag to true also helps, but that means going back on the
changes in HIVE-1841. I think we should continue to disable autocreate and use
schematool instead. So this is not a suitable workaround.
Until we have a fix in DN for this, I think we should downgrade the DN version
in hive to allow the use of postgres.
I will follow up with a bug in DN as well.
> Postgres db issues after Datanucleus 4.x upgrade
> ------------------------------------------------
>
> Key: HIVE-14322
> URL: https://issues.apache.org/jira/browse/HIVE-14322
> Project: Hive
> Issue Type: Bug
> Affects Versions: 2.0.0, 2.1.0, 2.0.1
> Reporter: Thejas M Nair
> Assignee: Thejas M Nair
>
> With the upgrade to datanucleus 4.x versions in HIVE-6113, hive does not
> work properly with postgres.
> The nullable fields in the database have string "NULL::character varying"
> instead of real NULL values. This causes various issues.
> One example is -
> {code}
> hive> create table t(i int);
> OK
> Time taken: 1.9 seconds
> hive> create view v as select * from t;
> OK
> Time taken: 0.542 seconds
> hive> select * from v;
> FAILED: SemanticException Unable to fetch table v.
> java.net.URISyntaxException: Relative path in absolute URI:
> NULL::character%20varying
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)