HIVE-21100: Allow flattening of table subdirectories resulted when using TEZ engine and UNION clause. #4730
Conversation
…ing TEZ engine and UNION clause.
asf-ci-hive
added
tests pending
tests unstable
and removed
tests unstable
tests pending
labels
|
|
||
| explain insert overwrite table test2 partition (dt='20230817') select ful.* from (select val from test2 where dt='20230816') ful left join (select val from test1 where dt='20230817') inc on ful.val=inc.val union all select test1.val from test1 where dt='20230817'; | ||
|
|
||
| insert overwrite table test2 partition (dt='20230817') select ful.* from (select val from test2 where dt='20230816') ful left join (select val from test1 where dt='20230817') inc on ful.val=inc.val union all select test1.val from test1 where dt='20230817'; |
There was a problem hiding this comment.
this test should be extended to certain scenarios:
- acid/mm/non-acid
- direct insert on/off
- union flattening on/off
create different tables for different scenarios:
union_target_acid_directinsert_flattened
union_target_mm_directinsert_flattened
union_target_nonacid_directinsert_flattened
union_target_acid_nodirectinsert_flattened
union_target_mm_nodirectinsert_flattened
union_target_nonacid_nodirectinsert_flattened
union_target_acid_directinsert_noflattened
union_target_mm_directinsert_noflattened
union_target_nonacid_directinsert_noflattened
union_target_acid_nodirectinsert_noflattened
union_target_mm_nodirectinsert_noflattened
union_target_nonacid_nodirectinsert_noflattened
|
|
||
| select * from union_target_acid_unflattened; | ||
|
|
||
| -- TESTS FOR DIRECT & NON FLATEENED |
asf-ci-hive
added
tests pending
tests unstable
and removed
tests unstable
tests pending
labels
|
Kudos, SonarCloud Quality Gate passed!
|
|
Have fixed the typo. The last failure was some |
…ing TEZ engine and UNION clause. (apache#4730). (Ayush Saxena, reviewed by Laszlo Bodor)
What changes were proposed in this pull request?
Allow to flatten subdir in case of UNION
Why are the changes needed?
To avoid Subdir in case of UNION queries for compar
Does this PR introduce any user-facing change?
Yes, if the config is turned on.
Is the change a dependency upgrade?
No
How was this patch tested?
UT