hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <>
Subject [jira] [Commented] (HIVE-14322) Postgres db issues after Datanucleus 4.x upgrade
Date Mon, 25 Jul 2016 20:39:20 GMT


Sergey Shelukhin commented on HIVE-14322:

It's suspicious that it would work with auto-create but not with a script, which has nothing
to do with postgres as such.
I wonder if the syntax in the script (""COLUMN_TYPE" character varying(128) DEFAULT NULL::character
varying) has anything to do with it? Should we change these to NULL and would it help?

Can you reference a DN bug if you file one?

> Postgres db issues after Datanucleus 4.x upgrade
> ------------------------------------------------
>                 Key: HIVE-14322
>                 URL:
>             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. Relative
path in absolute URI: NULL::character%20varying
> {code}

This message was sent by Atlassian JIRA

View raw message