[jira] [Commented] (HIVE-18137) Schema evolution: newly inserted column value in pre-existing partition is masked to null

["Zoltan Haindrich (JIRA)" <ji...@apache.org>]

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

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

[~ekoifman],[~ashutoshc]: not entirely sure why...but this have somehow changed during one of my changes...I consider it an improvement...

I've tried to follow the history....thru various refactors; renames/etc I've found an ancient version of this test which do had similar results:
https://github.com/apache/hive/blob/2f0339b08b375a1b656a178627600fc26c0a974c/ql/src/test/results/clientpositive/schema_evol_orc_nonvec_mapwork_part.q.out#L136


> 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)