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

Zoltan Haindrich commented on HIVE-18137:
-----------------------------------------

I've done a deep dive in the history but its pretty hard to uncover when this 
have changed...there are many renames...multiple different versions of the same 
test (vec/nonvec;part/table;orc/text,x/y) - this is kinda like a matrix test...

> Schema evolution: newly inserted column value in pre-existing partition is 
> masked to null
> -----------------------------------------------------------------------------------------
>
>                 Key: HIVE-18137
>                 URL: https://issues.apache.org/jira/browse/HIVE-18137
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Zoltan Haindrich
>
> {code}
> set hive.explain.user=false;
> set hive.fetch.task.conversion=none;
> set hive.mapred.mode=nonstrict;
> set hive.cli.print.header=true;
> SET hive.exec.schema.evolution=true;
> SET hive.vectorized.use.vectorized.input.format=true;
> SET hive.vectorized.use.vector.serde.deserialize=false;
> SET hive.vectorized.use.row.serde.deserialize=false;
> SET hive.vectorized.execution.enabled=false;
> set hive.exec.dynamic.partition.mode=nonstrict;
> set hive.metastore.disallow.incompatible.col.type.changes=true;
> set hive.default.fileformat=textfile;
> set hive.llap.io.enabled=false;
> CREATE TABLE part_add_int_permute_select(insert_num int, a INT, b STRING) 
> PARTITIONED BY(part INT);
> insert into table part_add_int_permute_select partition(part=1) VALUES (1, 
> 1111, 'new');
> alter table part_add_int_permute_select add columns(c int);
> insert into table part_add_int_permute_select partition(part=1) VALUES (2, 
> 2222, 'new', 3333);
> select insert_num,part,a,b,c from part_add_int_permute_select;
> {code}
> results for the last select:
> {code}
> 1      1       1111    new     NULL
> 2      1       2222    new     NULL
> {code}
> I think the following result should be expected:
> {code}
> 1      1       1111    new     NULL
> 2      1       2222    new     3333
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to